E-mail List Archives
Re: Build for the bugs?
Date: Feb 23, 2015 1:11AM
- Next message: Steve Faulkner: "Re: Build for the bugs?"
- Previous message: Olaf Drümmer: "Re: Build for the bugs?"
- Next message in Thread: Steve Faulkner: "Re: Build for the bugs?"
- Previous message in Thread: Olaf Drümmer: "Re: Build for the bugs?"
- View all messages in this Thread
On Sun, Feb 22, 2015 at 08:59:18AM -0500, Asa Baylus wrote:
> So what happens when we code to resolve a specific bug and our bug fix breaks the spec?
With browser bugs, many of us comment the hell out of our weird
If you use a well-known prefix like //XXX or //FIX, you can find them
later easily to remove the moment you can get away with it.
If say JAWS had a bug that NVDA didn't and you could not possibly write
code that worked for both of them? With browsers, popularity was
indeed a factor: if the Good Browser was Opera, it got the shaft :(
But usually it's one having a bug and the rest mostly conforming, so
then it's looking at "what do the clients use" and "does this seem like
it will be fixed by the vendor soon" and "does this vendor auto-update?"
At least, those are the kinds of questions that we go through.