Smae thing that Nvidia does with OpenGL. Their driver handles a lot erroneous out of spec behaviour so developers think their game works fine but the moment you run it on AMD or Intel GPUs, you get all sorts of issues because they actually implement the spec accurately.
This is like telling people that they are doing something wrong when they don’t “buy low and sell high” when they’re trading. Obviously. Issues with browser parity are born from a difficulty of the how and the when, not the what.
It’s so damn stupid. If your site works meaningfully differently in Firefox vs Chromium, you’re already doing something very, very wrong.
Yep, this is why at least for me when I develop websites I use Firefox first for development to make sure that the website runs on Firefox.
Chromium does a lot of heavy lifting to fix problems with websites which enables certain web developers to be lazy.
Smae thing that Nvidia does with OpenGL. Their driver handles a lot erroneous out of spec behaviour so developers think their game works fine but the moment you run it on AMD or Intel GPUs, you get all sorts of issues because they actually implement the spec accurately.
This is like telling people that they are doing something wrong when they don’t “buy low and sell high” when they’re trading. Obviously. Issues with browser parity are born from a difficulty of the how and the when, not the what.
The how is testing on one other browser.
What a novel idea.