I assure you, if you had developed against firefox first, you would have found "performance bugs" on chrome.
Source: I developed a web game.
Source: I developed a web game.
Testing in Firefox is a pretty good way to approximate standards compliance, and then you have to deal with bugs when running on Chrome, if you do it that way around.
Before that, some other update gave issues with some certificate.
Looking at all the issues this browser causes, and the very low usage, I'm not spending time tracking down what is going wrong.
Safari on iOS is such another problem child, but used high enough to justify the time to investigate and fix.
https://blog.mozilla.org/security/2016/10/24/distrusting-new...
>Looking at all the issues this browser causes, and the very low usage, I'm not spending time tracking down what is going wrong.
been hearing this for about a decade now...Your point of "been hearing this" is what?