3 ms·

I didn't get this at all from the article. He didn't say that other browsers are stupid, he said that they have bugs; the outline thing is a particularly nasty

by Touche 10y ago

I didn't get this at all from the article. He didn't say that other browsers are stupid, he said that they have bugs; the outline thing is a particularly nasty Firefox bug. It might also be a spec bug if the spec is not detailed enough on how to draw outlines; but it's also definitely a Firefox bug because it looks terrible. There's nothing wrong with calling a spade a spade.

Etzos 10y ago
A quick search turns up that it is indeed a Firefox bug and not a bug in the spec[0]. Honestly it is very disappointing that such an obvious issue has been left open for so long. This is part of a very old spec and that any browser doesn't have compliance with this is surprising. [0] https://bugzilla.mozilla.org/show_bug.cgi?id=266122 https://bugzilla.mozilla.org/show_bug.cgi?id=266122
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 :)

by Touche 10y ago

Etzos 10y ago

A quick search turns up that it is indeed a Firefox bug and not a bug in the spec[0]. Honestly it is very disappointing that such an obvious issue has been left open for so long. This is part of a very old spec and that any browser doesn't have compliance with this is surprising. [0] https://bugzilla.mozilla.org/show_bug.cgi?id=266122 https://bugzilla.mozilla.org/show_bug.cgi?id=266122

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 :)