Closed (fixed)
Project:
Footnotes
Version:
4.0.x-dev
Component:
Footnotes
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Feb 2026 at 15:41 UTC
Updated:
24 Apr 2026 at 05:00 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #3
scott_euser commentedComment #4
scott_euser commentedSeems like legitimate test failures...
Comment #5
scott_euser commentedComment #6
scott_euser commentedOkay tests passing now
Comment #7
scott_euser commentedVia such a giant report, quite a rabbit hole and dates back to the original footnotes grouping solution to handle multiple formatted text instance originally targeting 3x branch, but converting things to static. Moving back to NW as this is going to need more test coverage for such scenarios as clearly some areas not sufficiently covered.
Comment #8
scott_euser commentedOkay added some more test coverage to this now as well to areas it potentially affects
Comment #9
jan.fetalvero commentedComment #10
jan.fetalvero commentedTested on:
Drupal: 10.x
PHP: 8.x
Branch: 3572013-random-string (MR !96)
Testing process:
Created a test node with 500 footnotes to stress test the fix. Disabled the render cache to bypass Drupal caching so the filter runs on every request.
Node with 500 footnotes:

On the 4.0.x branch:

The footnote anchor IDs contain three parts a hash of the content, plus a trailing random string (e.g. rMl0OUTKAU0r) that is different on every single render:
id="footnoteref__MTx1WlRHW4R9vYOCTc9ymjiqo14pWER6-cMMosmYo0_rMl0OUTKAU0r"On the 3572013-random-string(MR !96) branch:

The random string is completely removed. The ID is now built only from the footnote number and a hash of the citation text:
id="footnoteref__MTx1WlRHW4R9vYOCTc9ymjiqo14pWER6-cMMosmYo0_1"Running the render multiple times produces identical IDs every time — the citation href and reference id always match.
Automated tests:

34/34 tests pass
5 JavaScript browser tests skipped
0 failures, 0 errors
Fix confirmed working. Setting to RTBC.
Comment #11
jan.fetalvero commentedComment #12
scott_euser commentedThank you very much for the thorough review, I know its quite time consuming, so really much appreciated. Because its quite big will still give it some more time; I'll set a reminder for about a month from now.
Comment #14
scott_euser commentedThanks again! Will leave this in dev for some time, then beta, then hopefully we can get to a more stable release.