Report Browser Bugs
Help browser makers plug the holes in their standards compliance by identifying and reporting bugs. We can’t overemphasize the importance of this simple, quiet activity.
Check your work first!
Naturally, it helps if the problems you’ve identified are actually browser bugs, not errors in your markup. First step: validate your XHTML to be certain it contains no errors, and check your CSS while you’re at it. Browser makers cannot be held responsible for the misbehavior or poor display of sites that use broken markup, invalid styles, or screwy scripts.
Tip: For one-click validation, install bookmarklets from Tantek Çelik. To “validate” your JavaScript/ECMAScript, be certain your browser is set to enable scripting and to show scripting error alerts, and test in more than one browser.
If your page validates and you’re sure the browser is getting it wrong, report standards-related bugs directly to the manufacturers using the special WaSP email addresses below.
Reporting bugs to Microsoft
To report browser bugs in MSIE5/6 for Windows or Mac OS, please register for IE Connect and sign up for the IE Public Feedback program.
Reporting bugs in Mozilla
Report Mozilla bugs at Bugzilla, Mozilla’s aptly named online bug tracking system.
Reporting bugs to Opera
To report bugs in Opera Software’s Opera 8/9 browser, please use the Opera bug tracking system.
Reporting bugs to the WebKit Open Source Project (including Safari)
To report a bug in the WebKit open source project, on which Apple’s Safari is based, visit the project’s bug reporting page.
Reporting bugs to Netscape
AOL will discontinue development of and support for all versions of the Netscape Navigator browser as of February 1, 2008.
Reporting bugs to KDE
To report a bug in the KDE browser, visit the KDE Bug Tracking System.
The Web Standards Project is a grassroots coalition fighting for standards which ensure simple, affordable access to web technologies for all.