Yes.

If it works on Chrome, no one cares or even tests for other things.

If there is a JS feature in Chrome they want to use, so it’s impossible to use other browsers (instead of looking wrong) people do it.

Performs fine in Chrome? Ship it.

Yes, Chrome is the new IE in that it’s the only browsers companies care about, just like IE was for a very long time.

Everything has to be Chrome compatible to succeed. That’s the benchmark, not what the spec says.

Not even close. IE 6 didn’t get any updates or new web features for years. It was closed source. It was dead and everyone used it. float:right; zoom:1; was a common necessity… to compare them is an insult to the immense progress and effort spent over the last 24 years… (yes chrome started in 2007, but the teams from Firefox get credit too, many of them went on to build chrome ). The open source movement won, IE is dead - MS shipped edge. We can argue about how Google is evil all day but it’s night and day compared to what the web was like in 2000

One issue I keep see cropping up with various corporate websites is they will only allow Chrome and will block any other browser. I would say in 9/10 cases, this isn't because the site uses features not supported in other browsers but rather, developers restrict it to Chrome because that's all their QA's test on.

No not even close by every single possible measure.

I was there, I suffered through it, Google would have to make TONS of hostile moves for that fact to change.

I have no interest in the arguments of a closed source subscription service that wants me to switch to the bundled browser of the wealthiest company on earth's most popular consumer OS, lecturing me about using the 4th wealthiest company on earth's browser that I freely installed.

The most important one from an anti-trust perspective, every device I've ever had Chrome on I've had to seek out and install/make default Chrome, that includes my mobile devices which used the manufactures browser by default.

If I want to use chromium I can, Safari has been VERY late in implementing certain industry spec standards (SSE's, web sockets, IndexedDB API, animations, relative color syntax, container queries, a bunch of <video> stuff, flexbox, the list goes on and on.)

As an example of how perfidious some of the discussions on web standards are, on Wikipedia:

https://en.wikipedia.org/wiki/Comparison_of_browser_engines

In teeny tiny font near the bottom:

"Given the market-share dominance of Blink-based browsers,[4] if Google chooses to not support a standard, like JPEG XL,[30][31] it will not become relevant on the Web.[30][31] Such standards are not listed in these tables."

So if Chrome implements something that Safari doesn't, then its a deficiency in Safari. If Safari supports something Chrome doesn't, its not relevant so will not appear in any comparison tables.

Chrome is 100% the new IE, as it is the being treated as the sole arbiter of what is a web standard or not.