Steps to reproduce issue:
1. Open
http://w3c.github.io/aria-in-html/#aria-touch in Chrome
2. The document scroll position will be set somewhere around section 2.10. instead of section 6. which corresponds to the #aria-touch fragment (i.e. that’s where the id="aria-touch" attribute is set).
What Chrome could do:
In the above example (and on many other sites, from my experience), the document’s height changes during page load (e.g. JS mutates the DOM structure, styles are applied dynamically, etc.). I think, these changes are the culprit of this issue. What Chrome could do, is, as long as the user doesn’t scroll manually during page load, enforce the correct scroll position
continuously, until the page “stabilizes”.
This is similar to what scroll anchoring does (which is behind flag), and it would be a big UX win for the user, I think. As of right now, URL fragments are unreliable, and an intervention is the only fix I can think of.