Web browsers should provide autocompletion for URL fragments for the current page.
Also, I should be able to address a fragment *just* by typing "#" + fragment_identifier, instead of current_url + "#" + fragment_identifier.
@raucao @lanodan okay, maybe by filtering with some heuristics like "is this ID the ID of a heading?" Actually, just building up an autocompletion list on that alone would probably get us the 80 of 80/20.
Aside from that, a lot of the pages that have unusable anchors are pages where people are unlikely to be using the feature. E.g. checking the homepage for new Reddit—an egregious 1100+ autogenerated element IDs. But there's hardly a use case for trying to address something there, anyway.
We'd probably have seen a similar feedback loop for rel=next if mainstream browsers actually had UI for it. (That's not necessarily a lost cause even now. Chrome could add it tomorrow—and people would say the devs are geniuses and then go add this "new" thing to all their sites.)
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!