This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Using replaceState, something like http://whatwg.org/C#parsing instead of http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html#parsing would be super. Then as you scroll the URL should change. This is probably less important now that with the new toolchain the multipage sectioning is stable, and so you are less likely to copy-and-paste a URL that becomes "wrong" (fixed via redirects) after a month or two.
Domenic if you still think we should do this, I wonder if in order to of make potential contributors more aware of it—and so maybe find somebody interested enough by it to work on contributing a patch—we should consider moving it over to https://github.com/whatwg/html/issues and labeling it with “good first bug”.
I've had this in the back of my head for a while. I guess I no longer thing it's worth it. It causes consumers of that link to *always* get a redirect, instead of only if content has moved since last time. That's not a great tradeoff.