Because the Chrome team is consistently the fastest at supporting newly introduced standards.
A more accurate reading would be: "Sorry, this website only works in Chrome right now. Try Firefox in two weeks, and Edge and Safari in about six months".
Even though some people have changed their Firefox user agent and found that the web page still works under Firefox. Chrome isn't the only browser doing things to extend the web. Firefox and Mozilla work on new features too. Chrome didn't come up with WebAssembly, Mozilla developers did. Edge isn't as behind as it once was either, pretty sure they called it Edge for "Bleeding Edge" and you can see the source for their JavaScript Engine on GitHub.
I installed a Firefox plugin to support my YubiKey for two factor authentication. It worked fine for github, but Google login just locked me out saying Firefox doesn't support it.
So yeah, I blame the website owners, which means Google.
> Because the Chrome team is consistently the fastest at supporting newly introduced standards.
Yeah, that's an interesting way to see it when Google/Chrome dominates/finances the whole WHATWG web "standardization" process directly after "what Webkit is doing". Not saying there isn't bona fide work, but basically there are many ways to derail meaningful standardization efforts other than by not playing ball: by making it so fscking complicated and prohibitively expensive that nobody can't compete. HTML is over 25 years old. There should be no need to rush features all the time. If that's happening anyway (WHATWG's "living standard" nonsense), then something is seriously wrong with the scope and organization of WHATWG's work.
Because the Chrome team is consistently the fastest at supporting newly introduced standards.
A more accurate reading would be: "Sorry, this website only works in Chrome right now. Try Firefox in two weeks, and Edge and Safari in about six months".