4 ms·

My opposite viewpoint as a web developer: Chrome is faster and renders better than Firefox is pretty much every way. Safari delivers faithful color reproductio

by akanet 10y ago

My opposite viewpoint as a web developer: Chrome is faster and renders better than Firefox is pretty much every way. Safari delivers faithful color reproduction and speed. I spent 10x as much time fixing Firefox rendering issues compared to every other browser, including Microsoft Edge. Firefox has lost its edge. I do miss tree style tabs, though.

chrismorgan 10y ago
Firefox has been my primary browser since 0.93, so I am naturally biased, but here is my anecdotal position. I develop sites in Firefox and then go for compatibility checking in other browsers. Edge is normally fine. Chrome is horrible. Atrocious. Abysmal. It implements lots of new features, but they are just so regularly buggy or badly implemented. To select the example I remember the clearest (there have been many more over the years): I went to use flexbox on one site and Firefox agreed with the spec (and what was obvious) on the treatment of some major item sizing issue while Chrome did something altogether different which I really couldn’t think of any justification for and which made flexbox a non-starter in that case. A year or two later they had fixed it in Chrome, but I’ve ever found it like that: Firefox has a slower rate of implementation, but normally implements things well; WebKit/Blink has a faster rate of implementation, but breaks things often (even with a handful of serious bugs in production releases that broke entire websites completely) and has always felt like a toy, rather than a serious, stable browser engine.
- andrewclunn 10y ago
  Try doing flex structures within flex structures in Firefox. Now tell me that Chrome is the buggy one.
- akanet 10y ago
  I really can't agree - one major area is CSS 3D transforms. Firefox recently broke stacking order (again) context in 3D in the 49 release, and continues to have very poor aliasing artifacts. Chrome/Safari/Edge have pretty solid implementations. Here's just one of the many bugs filed on the topic: https://bugzilla.mozilla.org/show_bug.cgi?id=1187209 https://bugzilla.mozilla.org/show_bug.cgi?id=1187209. Firefox can have major (breaking) paint bugs filed and have "Status: NEW" for basically an entire year.

by akanet 10y ago

chrismorgan 10y ago

Firefox has been my primary browser since 0.93, so I am naturally biased, but here is my anecdotal position. I develop sites in Firefox and then go for compatibility checking in other browsers. Edge is normally fine. Chrome is horrible. Atrocious. Abysmal. It implements lots of new features, but they are just so regularly buggy or badly implemented. To select the example I remember the clearest (there have been many more over the years): I went to use flexbox on one site and Firefox agreed with the spec (and what was obvious) on the treatment of some major item sizing issue while Chrome did something altogether different which I really couldn’t think of any justification for and which made flexbox a non-starter in that case. A year or two later they had fixed it in Chrome, but I’ve ever found it like that: Firefox has a slower rate of implementation, but normally implements things well; WebKit/Blink has a faster rate of implementation, but breaks things often (even with a handful of serious bugs in production releases that broke entire websites completely) and has always felt like a toy, rather than a serious, stable browser engine.

andrewclunn 10y ago
Try doing flex structures within flex structures in Firefox. Now tell me that Chrome is the buggy one.
akanet 10y ago
I really can't agree - one major area is CSS 3D transforms. Firefox recently broke stacking order (again) context in 3D in the 49 release, and continues to have very poor aliasing artifacts. Chrome/Safari/Edge have pretty solid implementations. Here's just one of the many bugs filed on the topic: https://bugzilla.mozilla.org/show_bug.cgi?id=1187209 https://bugzilla.mozilla.org/show_bug.cgi?id=1187209. Firefox can have major (breaking) paint bugs filed and have "Status: NEW" for basically an entire year.