Tuesday, December 30th, 2008>p>John Resig has laid out his thoughts on a Web Developer’s Responsibility, and it comes down to working with various up and coming browser versions and filing bugs:
It’s safe to say that the biggest tax on a web developer is spending so much time dealing with browser bugs and incompatibilities. Thus it has become the favorite past-time of all web developers to complain about having to deal with them. Browser bugs are annoying, frustrating, and make your job incredibly difficult.
Because browser bugs are so frustrating and such a burden on top of normal development it should be the responsibility of every web developer to make sure that the browsers they develop for are able to find and fix their bugs. By taking responsibility for the bugs that you find – and to not assume that “someone else will find it” – will accelerate the rate at which browsers can improve.
The solution to helping browsers is two-fold: 1) Every time you find a browser bug, file a bug report to the respective browser. 2) Actively test your sites in the latest builds of the major browsers.
The vast majority of web developers have never filed a bug report with a browser vendor – or even used a nightly version of a browser – which is a shame. If you think about it there are few who are more qualified to assess what is going wrong in a browser than those who spend every day developing for them.
I’m especially surprised when I see professional developers not filing bugs with browsers, or testing on nightlies. Since one of the primary tasks of most developers is to paper over cross-browser issues it becomes in their best interest to see the number of bugs reduced (and making their job dramatically simpler).
Now, instead of just saying “go do it”, John gives information on how to file a bug, where to go to do it, providing a good simple test case, and arguing for a bug.
He then shows examples of bugs that he has filed across browsers, and asks us all to wear them like badges.
So, got any badges? Been frustrated when filing a bug? What’s the weirdest bug you have ever seen (sorry, interview question there).