-
Bug
-
Resolution: Unresolved
-
Medium
-
Severity 2 - Major
Issue Summary
The Events API is not working in dynamic content macros inside the JSM Article view when the customer has a custom domain.
Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('<URL>') does not match the recipient window's origin ('<URL>').
Steps to Reproduce
- Setup a Confluence Space as Knowledge Base in a Jira Service Management project
- Create a custom domain for the Service Portal
- Install the App
- Add some language macros on the page, eg. german & english
- view this page in the Knowledge base view in the Jira Service Management Customer Portal
- The language macros communicate via the JS event API to identify which language to show
Other responses for window.AP. (based on the test with another app)
undefined
Expected Results
The app should work the same way also from Custom domains.
Actual Results
Failed to execute ‘postMessage' on 'DOMWindow': The target origin provided ('<URL>') does not match the recipient window's origin ('<URL>'). in the browser console. → the macros don’t show content. happens in the all.js, you can find it in the logs.
Workaround
Use the app from the normal domain (domain.atlassian.net) instead of custom domains.
[ECO-194] Confluence Connect Javascript API Events not are working in JSM article view with custom domain.
| Workflow | Original: JAC Bug Workflow v3 [ 4444646 ] | New: JAC Bug Workflow v4 [ 4567125 ] |
| Description |
Original:
h3. Issue Summary
The [Events|https://developer.atlassian.com/cloud/confluence/jsapi/events/] API is not working in dynamic content macros inside the JSM Article view when the customer has a custom domain. {{Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('<URL>') does not match the recipient window's origin ('<URL>').}} h3. Steps to Reproduce # Setup a Confluence Space as Knowledge Base in a Jira Service Management project # Create a custom domain for the Service Portal # Install the App # Add some language macros on the page, eg. german & english # view this page in the Knowledge base view in the Jira Service Management Customer Portal # The language macros communicate via the [JS event API|https://developer.atlassian.com/cloud/confluence/jsapi/events/] to identify which language to show Other responses for *window.AP.* (based on the test with another app) {code:java} undefined{code} h3. Expected Results The app should work the same way also from Custom domains. h3. Actual Results {{Failed to execute ‘postMessage' on 'DOMWindow': The target origin provided ('<URL>') does not match the recipient window's origin ('<URL>').}} in the browser console. → the macros don’t show content. happens in the all.js, you can find it in the logs. h3. Workaround Use the app from the normal domain (domain.atlassian.net) instead of custom domains. |
New:
h3. Issue Summary
The [Events|https://developer.atlassian.com/cloud/confluence/jsapi/events/] API is not working in dynamic content macros inside the JSM Article view when the customer has a custom domain. {{Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('<URL>') does not match the recipient window's origin ('<URL>').}} h3. Steps to Reproduce # Setup a Confluence Space as Knowledge Base in a Jira Service Management project # Create a custom domain for the Service Portal # Install the App # Add some language macros on the page, eg. german & english # view this page in the Knowledge base view in the Jira Service Management Customer Portal # The language macros communicate via the [JS event API|https://developer.atlassian.com/cloud/confluence/jsapi/events/] to identify which language to show Other responses for *window.AP.* (based on the test with another app) {code:java} undefined{code} h3. Expected Results The app should work the same way also from Custom domains. h3. Actual Results {{Failed to execute ‘postMessage' on 'DOMWindow': The target origin provided ('<URL>') does not match the recipient window's origin ('<URL>').}} in the browser console. → the macros don’t show content. happens in the all.js, you can find it in the logs. h3. Workaround Use the app from the normal domain (domain.atlassian.net) instead of custom domains. |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Labels | New: ecohelp |
I've just upvoted this issue. We pay for Karma, a Confluence marketplace app which allows for greater control of branding and styling Confluence pages. We wrap all of our Knowledge Base articles in this app for cohesive and upscaled branding. We just elected to use a custom domain because our customers keep requesting access to our Jira/Confluence when they forget the /servicedesk in the URL, but then we realized none of our knowledge base content loads anymore with the custom domain active. We've had to disable the custom domain because of this issue.
Please fix this, guys. Come on.