> The point is they are not even compliment to their "own" spec. They are part of whatwg.
I think web devs have too much faith in the "standard"; the WHATWG specifies anything supported by two implementations, and with Google controlling Mozilla that already feels somewhat unfair...
> Write a page on chrome, works 90% on Firefox. But will likely works 10% on safari.
Disregarding the issue that you're writing pages that only 90% work on anything but Chrome... do you have any examples of Safari misbehaving?
The ios safari lies you about (or simply bugged out) video play event, display video element on play event will show a blank screen to user. This never happen in any other browser(including those china vendor browsers) except safari. To make this worse, you can't make a unloaded video element on safari to have transparent background so user will definitely see a black square unless you add a delay to mitigate the problem.(Most players already do it, but it's still a pain if you need to make one from scratch)
I think web devs have too much faith in the "standard"; the WHATWG specifies anything supported by two implementations, and with Google controlling Mozilla that already feels somewhat unfair...
> Write a page on chrome, works 90% on Firefox. But will likely works 10% on safari.
Disregarding the issue that you're writing pages that only 90% work on anything but Chrome... do you have any examples of Safari misbehaving?