3 ms·
I agree that calling out bugs, especially if they've been reported and ignored, is worthwhile. That said, I think what the parent comment is saying is that Chr
by bhauer 10y ago
I agree that calling out bugs, especially if they've been reported and ignored, is worthwhile.
That said, I think what the parent comment is saying is that Chrome too has bugs and a web developer who exclusively tests in Chrome forgives those bugs as "just the way HTML rendering works." This makes the developer effectively blind to Chrome's defects.
A developer who uses Firefox exclusively will have a similar feeling of privileged disdain for Chrome's bugs: "How can Google ship a browser with this problem? This is unacceptably broken!"
I know I felt that way for ages with Chrome's font rendering [1]. Chrome's font rendering was so poor compared to Firefox that it was difficult for me to use even for short bursts of testing. Although admittedly—and in a way confirming my point—those who used Chrome regularly were conditioned to its rendering and in some cases didn't even perceive the difference when comparing them side-by-side.
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=25541 https://bugs.chromium.org/p/chromium/issues/detail?id=25541
- insin 10y ago> A developer who uses Firefox exclusively will have a similar feeling of privileged disdain for Chrome's bugs: "How can Google ship a browser with this problem? This is unacceptably broken!" I don't know about its bugs, but that's pretty much how I feel about Chrome's address bar when I'm testing apps in it :)