-
Bug
-
Resolution: Won't Fix
-
Medium
-
Severity 3 - Minor
-
Confluence add-ons are being moved from our older P2 plugins framework over to our more modern Connect framework. The overall result will be better performance and functionality in Confluence Cloud. It does, however, mean that we’ll occasionally need to deprecate functionality that was previously available.
In this case, it won’t be possible to link to the anchor macro when it’s embedded within a macro provided by a Connect add-on. Links to anchors of this type will instead link to the relevant page rather than linking directly to the specific area of the content where the anchor is positioned.
What can I do?
If the anchor doesn't need to be inside the body of the Connect macro, we suggest moving it outside the macro and to a relevant location on the page.
If you have any concerns or questions, please feel free to comment on this issue.
The technical info
Confluence Cloud macros (dynamic macros) are rendered inside an iframe. If the macro tries to render an anchor link, or includes a macro that generates an anchor link, the link can't be navigated to using the standard hash tag navigation.
For example:
- Create a dynamic macro (any dynamic macro will expose this issue).
- Insert an anchor macro (this will render a named anchor in to the page)
Result:
- Expected: navigating to the page with #anchorName should scroll to the anchor
- Actual: the #anchorName is ignored and the page is not scrolled
Reason:
- The anchor is rendered inside the iframe and scrolling to anchors contained in child iframes isn't supported by default.