4 ms·
Was going to say much the same thing. I've been a full-time Firefox user for 10+ years. I've also worked on web apps and tested against Firefox, Chrome, IE (and
by GordonS 7y ago
Was going to say much the same thing. I've been a full-time Firefox user for 10+ years. I've also worked on web apps and tested against Firefox, Chrome, IE (and later Edge), for 10+ years.
In all that time, I don't think I've ever seen a Firefox-specific bug or layout issue.
I saw them on IE all the time (obviously), sometimes in Edge, rarely in Chrome, and never in Firefox.
- Lendal 7y agoMe either. When something doesn't work it's almost always because of Privacy Badger. If I'm really curious I'll whitelist it to see if that does the trick. Otherwise I might report the bug to the site, but typically there's just not enough time in my life to waste on broken web sites. People hold on to this belief that Google is infallible because they're rich and they put together a marketing campaign some years back to convince people that only smart people work there. I believe the truth is exactly the opposite.
- kiaulen 7y agoAlso a full time Firefox user. Another bug that I believe is actually Firefox doing the right thing: if you make an event handler function but give it no parameters, Firefox will have no local named event. Chrome will create an event variable for you. Caused several "Firefox bugs" in our app.
- DCoder 7y agoThe behaviour you're referring to is actually a global property `window.event` [0]. Although it's part of the DOM spec, it's only there for historical reasons and should definitely be avoided. [0]: https://developer.mozilla.org/en-US/docs/Web/API/Window/event https://developer.mozilla.org/en-US/docs/Web/API/Window/even...