Absolutely! Launching a change to the web platform is a long, arduous process. This feature is currently taking the very early first steps.
For more details, see https://www.chromium.org/blink/launching-features.
Having some feature like this for the web would in itself be good, just claiming a key in the hash part just for this would (and I know that hash doesn't really have a format so "it's not a key" etc, but it does gets used that way).
A proposition: instead of using plain 'targetText' how about having some prefix for all Chromium's claims in the hash part so that the front-end (framework) developers can filter these out without needing to keep a list?
Good luck!
> ... and make half the world use it.
vs.
> Add about:flag for Scroll-To-Text
> Adding chrome://flag to allow users (particularly on Mobile) to easily enable and test the feature.
(Commit message via https://chromium-review.googlesource.com/c/chromium/src/+/14...)
So nobody will use the feature unless they explicitly choose to.
Regarding URL hash abuse elsewhere: this current development in Chromium is different from front-end frameworks and specific websites doing it because SomeSite can't break OtherSite while both having a different way to handle the hash.
Now Chromium randomly claims part of the hash which others now need a workaround for? Are these devs serious?
edit: dear downvoter, explain yourself :)