Issue Summary

Forge macros fail to load when the page that contains them is inside an Include Page macro or embedded page link.

This is reproducible on Data Center: No

Steps to Reproduce

1. Create Page A and add a Forge macro on it
2. Create Page B and add an Include Page macro on it, pointing to Page A
3. Save Page B and load it in view mode

Replace the Include Page macro with the embedded view link mode to reproduce it using that feature.

Expected Results

The Forge macro from Page A loads and renders correctly in Page B.

Actual Results

The Forge macro fails to load. The results are the following:

1. When using the Include Page macro, the macro name is shown instead of its rendered view
   • Refer to the screenshots for more details.
2. When using the embedded link view mode, the macro fails to load and throws a CSP violation on the developer console:

   Refused to frame 'https://*.cdn.prod.atlassian-dev.net/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self' *.atlassian.net bitbucket.org *.jira.com *.atlassian.com <>.atlassian.net".
   

Note: This issue happens with both Custom UI and UI Kit macros, and it also affects plugins using this Atlaskit package:

• https://atlaskit.atlassian.com/packages/confluence/embedded-confluence-public

Workaround

Use the embed view option of the Smart Links.