Hi Confluence Community,
Since the Panel macro UI was updated in the new editor (with the new inline toolbar showing Remix, Custom, Emoji, and colour swatches), headings placed inside Panel macros no longer generate working anchor links for the Table of Contents macro.
What happens:
A Table of Contents macro is placed at the top of the page
Section headings (H2, H3 etc.) are inside Panel macros for visual styling
The TOC lists the headings correctly, but clicking them does not jump to the section — the anchor link is broken
Expected behaviour:
Clicking a heading in the TOC should scroll the page to that section, regardless of whether the heading is inside a Panel macro or not.
Before the Panel UI update, this worked correctly. The issue appears to have been introduced with the new inline panel toolbar.
Workaround:
Moving headings outside the Panel macro restores TOC functionality, but loses the visual styling effect.
Environment:
Confluence Cloud
New editor (fabric editor)
Table of Contents macro + Panel macro combination
Has anyone else experienced this? Is there a fix planned?
Thanks
Hi @Hayato Nagata ,
The same symptom is already tracked in CONFCLOUD-81032, although the public bug currently describes headings inside deprecated or migrated Panel macros. It remains unresolved and there is no published fix date.
To confirm whether this is the existing defect or a new regression in the current Panel element, create a blank page with a new Table of Contents, insert a brand-new Panel, add one H2 heading, publish, and test the link.
For now, keeping the heading outside the Panel remains the safe workaround. The Table of Contents macro is intended to generate working links to headings on the page, so listing a heading without navigating to it is not expected behaviour.
Hey @Hayato Nagata ,
I've managed to find this bug report, but this is related to converting pages from the legacy editor to the new one: CONFCLOUD-82026: TOC links don't work for headings inside classic Panel macros after converting Legacy page to New Editor
Are you saying this is also reproducible when creating new pages?
If so, and if you're on a paid plan, you could reach out to Atlassian Support and ask them to confirm this behavior and potentially create a new bug report.
Cheers,
Tobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.