There is standard, and standard as previously Chrome only feature that Firefox felt pressured to implement and was then a posteriori made into a standard.

Because (Unpopular): I believe the standard should primarily cover how the overlapping functionality works, and refrain from limiting or prescribing the extent of functionality.

Comparing: If I build a HTTP API, I don’t have to support the DELETE verb for any endpoints. I can support ENCHANT if I want magic that other servers don’t have. But if I use GET, the endpoint handler should be idempotent. That’s the kind of standard I appreciate.

I don’t see any realistic win-win otherwise. Either you hold Chrome back from implementing new crap, or you force Safari to implement stuff they don’t want to. The efficient number of browser vendors seems to be small, so I think the standard body has just overplayed it’s hand.

It's not about tech issues. It's about pushing non-standard behavior. There are so many things Chrome implement and people start using, that other browsers have then to call them "standard" and make a similar implementation.

But even worse, since Google also is controlling some of the biggest websites, they can use this functionality and cripple other browsers for not supporting their "standards". Like YT has been horrendously slow on Fx for years. Not based on Fx being slow, but YT having implementation details that happen to work well on their own browser..

Like with IE that is the next step.

Once competition is utterly crushed, do you think Google "can defend" using tens of millions a year on this?

Microsoft "could not" and they have a much stronger history of maintaining stuff.

Why then would I think that a company that cannot even properly maintain their main public facing property, the search engine?

You know it used to be superior, today it is utterly meh, and no it isn't search spam sites, it is failing to acknowledge doublequotes and the verbatim setting. A billion spam sites cannot break that. Lack of competition can though.