Support rendering Forge app macros in Embedded Confluence

Forge Adopting Forge from Connect
, ,
1

Hello,

We use the Embedded Confluence API (@atlaskit/embedded-confluence, ViewPage) to display Confluence Cloud pages on our own external web domain (e.g. *.example.com). The page renders in an iframe whose top‑level document is the external site.

As apps migrate Connect→Forge, content that rendered on externally‑published pages for a long time suddenly breaks, with no change to the customer’s content. We hit this with a real customer whose entire public documentation broke after a vendor’s Connect→Forge migration.

Forge app macros (Custom UI / UI Kit) can’t render when a Confluence page is embedded or published outside Atlassian domains via the Embedded Confluence API (@atlaskit/embedded-confluence). The Forge iframe’s CSP frame-ancestors 'self' *.atlassian.net bitbucket.org *.jira.com *.atlassian.com blocks embedding on any non‑Atlassian domain, so the macro shows the browser’s “refused to connect”.

2

Hey @RahimHamani , could you open an Ecosystem Support Request for this one? If you have a sample app that can reproduce this as well, that’d be really helpful. I’ve just tested this locally and a basic Forge macro using @atlaskit/embedded-confluence embeds ok on my localhost, as well as a tunnelled HTTPS URL.

We’re keen to get to the bottom of this one with you. Thanks!

3

Not 100% related, but a explanation from a Vendor that broke customers/other vendors export support with the Connect->Forge transition.

But we certain broke some customers macro’s “exports” with the transition to Forge:

Basically, in Forge we ‘exported’ the macro as HTML, which 3rd party tools like the K15t Scoll view apps, or Atlassians own HTML export could export.

With Forge, we broke that:

  • The built-in Confluence PDF exporter got better way better, so that part works.
  • However, other export formats, like 3rd party tools and Atlassians own HTML export cannot use the ‘regular’ Forge view and require an ADF output from our macro.
  • However, ADF is to limited to properly render our macro. Even worse, if we provide a ADF render then the Confluence PDF exporter will use it and degrade.

So, currently we have the choice of:

  • Provide a limited ADF export for our Forge macro: But it won’t reach the old quality. And worst, it degrades the native Confluence PDF export, as it now goes the ADF route.
  • Provide no ADF export: Then the Confluence PDF export renders decently, but 3rd parties and other export formats fail.

We currently decided not add a ADF export and have a nice Confluence PDF export over supporting other exports / integrations.