We use in-page anchors on Omnipedia for a number of crucial UI interactions, especially on mobile, to enable various things to work even if JavaScript doesn't execute (e.g. the sidebar menu shows itself via CSS when #menu is present in the window location) by use of the :target selector. Turbo exhibits some unexpected behaviour compared to default browser behaviours; notably:
hashchange events are triggered twice during restoration visits.:target doesn't begin to match if hash added by a Turbo click.See above.
It looks like pull request #1125: Improve handling of anchor links and hashchange events fixes items 1 and 2 so we can either wait for that to be merged or patch Turbo ourselves; item 3 - :target not matching - seems like it might be difficult or impossible for them to implement cleanly as browsers don't expose a way to affect this directly, but it is possible to hack it in by programmatically clicking a link that Turbo isn't attached to, ugly though that might be.
:target to the targeted element · Issue #592Unclear.
Stuff begins to work as expected.
None?
None.
Postponed
2.0
Code
Issues #3416085 & #3422964: Added Turbo patches and documentation for.