Details
-
Bug
-
Resolution: Fixed
-
Major
-
Rendering in the platform
-
None
-
Integration
-
N/A
-
N/A
-
Pull Request accepted
-
Description
Included document should use the same IdGenerator than root document.
Here are some solutions:
- an api to provide the IdGenerator to the parser and make include macro give the root document IdGenerator to the parser
- store the IdGenerator in the Execution context (but this means add another dependency to rendering module)
- regenerate included XDOM ids in the include macro
- re-check and fix all ids in the renderer (which means all renderers need to take care of that)
- completely remove ids from XDOM/parsers and generate then in the renderer (but this mean we need to find another way to support internal link to other blocks, we already tried that...)
Attachments
Issue Links
- causes
-
CONFLUENCE-103 NoSuchMethodError in ConfluenceXWikiGeneratorListener in XWiki 13.10.4+/14.2+
- Closed
- is duplicated by
-
XRENDERING-578 Header anchors should be unique
- Closed
-
XWIKI-19535 Heading ids are not necessarily unique when using the include or display macro
- Closed
-
XRENDERING-461 TOC macro can generate invalid links when there are included pages
- Closed
- is related to
-
XRENDERING-3 Generated header id should be forced unique
- Closed
- relates to
-
XWIKI-15289 HTML headings are not correctly rendered in templates
- Open
-
XWIKI-6721 The include and display macros should have an option to filter out the first heading in the included document or section
- Closed