[jchw]

In general this would be a good thing, but not the way Safari does it. Why? Well, because eventually, almost everything Safari doesn't implement does get implemented in Safari, and because some of their longer running omissions smell suspiciously like conflicts of interest that hurt the ecosystem. A lot of people are incorrectly under the impression that Safari finally supports WebM and Opus, but it only does so on macOS (and every time I point this out, someone under that impression claims it has changed recently, and it never has; it's like Apple wants you to think it's supported.) Not to mention their "great" influence on the WebGPU standard and any other number of weird omissions and quirks in Safari.

It's annoying that I need Apple hardware to make sure my web applications work in Safari when I basically never need to specifically test Chrome or Firefox.