Inline Macro Displays Differently When Nested in Rich Macros (ADF Export Issue)

I’m using Forge Custom UI for macros and noticed some strange behavior. Inline macros render correctly when they appear directly on a page, but when the same macro is nested inside a rich macro (for example, inside a Panel), the display is different because it uses the ADF export (with export type other). This results in inconsistent rendering of the same macro depending on where it’s placed, which doesn’t seem logical especially that the not nested case uses react but the adf export is limited.

Is there any known solution or workaround for this inconsistency?

Hi @SamiBelHajHassine ,

I believe you are looking for this EAP to release Log in with Atlassian account

Which is planned to release in Jan 2026.

Cheers
Ben

1 Like

@Benny Thanks for the update! Is there any workaround available in the meantime until it’s officially released?
By the way, does that ticket cover :

  • inline macros nested within bodied macros,
  • bodied macros nested within other bodied macros,
  • or both?

Greatly appreciated sir !

Hi @SamiBelHajHassine just to clarify, the EAP linked above is to support embedded Forge content (i.e macros within macros). This is semi-related to nested macros; in that it allows for a 1-level embedding of forge content inside parent forge content; but may not be applicable for the scenario you described above.

Your use case looks to be with rendering your custom ui macro inside a native Confluence panel. I think for this scenario we should can raise this with our Confluence page experience team to see if this is a known issue or if there are any workarounds from your end and/or easy fixes from their end.

I’ll ping the relevant team and get them to respond here once they have investigated.

1 Like