This is where Chrome and IE 6 look very similar.
Meanwhile. Google tried to break that by funding Firefox. Eventually they decided they needed to do it themselves. They probably felt that Firefox was not moving fast enough.
Nowadays browsers achieve pixel perfect positioning and compatibility with each other.
The vendor, who works heavily in Chrome, was gobsmacked and their response was basically "well, yeah, but who uses Internet Explorer anymore?" to which we had to say that's fine, well, and good, but we must support IE10+/Edge.
It's an entirely different thing to just create a great product that people want to use instead of "being forced to" use. Firefox has been dragging itself behind for a long time and was nowhere near enough competitive as a whole package. Quantum has changed things but there are still some rough edges that need polishing (e.g. sometimes it just likes to freeze the tab completely). Chrome's web development tools are IMO top notch and I'd say it is the biggest reason why all the development happens on Chrome.
PS. This message is written on Firefox Quantum.
"Hangouts video and voice calls don't work in Firefox for now. Google is working to fix this as soon as possible. Until then, use a different supported browser."
It's been over a year! They can't really be "working to fix this as soon as possible", can they?
I think video might actually be working, but phone calls (via Google Voice or Google Fi) aren't and that is the message I get.
Phone calls from my computer (with my own number) were nice until they stopped working. Now I just open Chrome when I need that, but it would be nice to have it working in FF.
That's three for three. Chrome only scores one out of three.
In fact, in my own work I have to test Chrome first because I've learned the hard way that Chrome will surprise you with the weirdest bugs.
Recently I delved into the rabbit hole that is the Web Audio API. It exists... but apparently it's completely broken because Google shipped a half-assed implementation before the standards were ready.
Mozilla hurriedly did the same out of fear of losing market share, and now the spec is an absolute mess. The audio latency is on the order of 500-1000ms on average.
A solution to the latency issue was finally hammered out, but now the API is dead in the water and no one is implementing the new spec. Thanks, Google!