Browser on which this bug occurs
Mozilla Firefox
Expected Behavior
Actual Behavior
On at least one of the two pages (essentially random, decided during build-time), the navigation won't work. On both pages, the navigation links to #security, but the IDs are generated as #security and #security-2 (or similar).
Extra Details
This is because the headings have a slightly broken ID generation for de-duplication. In case of "security", the entire website has three headings. To prevent collision, the pages are generated with globally unique IDs ("security", "security-2", "security-3"). The navigation component tries the same, but only local to the page.
The ID generation for the headings should happen locally to the page as well.
Browser on which this bug occurs
Mozilla Firefox
Expected Behavior
Actual Behavior
On at least one of the two pages (essentially random, decided during build-time), the navigation won't work. On both pages, the navigation links to
#security, but the IDs are generated as#securityand#security-2(or similar).Extra Details
This is because the headings have a slightly broken ID generation for de-duplication. In case of "security", the entire website has three headings. To prevent collision, the pages are generated with globally unique IDs ("security", "security-2", "security-3"). The navigation component tries the same, but only local to the page.
The ID generation for the headings should happen locally to the page as well.