A standard designed by people from Google, discussed exclusively by people from Google, fast tracked into Chrome by people from Google and then released in Chro

A standard designed by people from Google, discussed exclusively by people from Google, fast tracked into Chrome by people from Google and then released in Chrome with utter disregard to any issues raised by other browser vendors does not a standard make. Unfortunately, since most web devs develop under Chrome (and rarely if ever test under other browsers) this perpetuates the myth that "Safari is holding the web back" or "Firefox is slow and doesn't implement standards fast enough". Here's total Web Apis counts in different web browsers: [1] - Chrome: 7106 - Firefox: 6376 - Safari: 6130 Of them: browser-specific APIs that developers cannot reasonably assume are a part of the web platform: - Chrome: 949 - Firefox: 507 - Safari: 546 And in 2017-2018 Chrome removed over a thousand APIs that were only implemented in Chrome, but were assumed to be standards" [1] And if you look at the omissions tab, you'll see that Firefox and Safari and not too far behind Chrome. But they are very wary of implementing quite a few standards just because Chrome fast tracked them (Constructible Stylesheets? Safari flat out refused to implement them. Signed HTTP exchanges? Mozilla considers them harmful and will not implement etc. etc.) [1] https://web-confluence.appspot.com/#!/confluence https://web-confluence.appspot.com/#!/confluence