How Web Standards Work 1. design a flawed API (it's fine! APIs are hard) 2. ship it in the most-used browser, despite objections 3. get cross-browser working group to fix the API 4. oops, too late, that would break the web
If anyone is curious, I did offer feedback on why document dot aSS is bad (leaving aside the extremely questionable/dangerous way that stylesheets are added to nodes): github.com/WICG/construct… Just in case you were about to tell me to get more involved instead of shitposting
And that's why Chrome's cowboy attitude to shipping features before they are are ready and then complaining when other browsers don't implement them is bad. Hope they'll learn their lesson one of these days.