MozillaZine

Reporting DOM Bugs? Be Sure to Read This!

Monday November 8th, 1999

Eric Krock has a request for anyone report DOM bugs:

"Please bookmark the below URLs!!!

If you hit a page that doesn't display well or has JavaScript errors in Nav5 (Mozilla) because the page uses MS IE4/5 DOM features, Nav4 Layer DOM features, or the LAYER/ILAYER tag, DON'T FILE A BUG in Bugzilla. Instead, use the below email creation templates to send an email to the page's owner asking them to upgrade the page to support W3C standards.

If the page supports IE4/5 but not HTML 4.0/W3C DOM:
http://sites.netscape.net/ekrock/fixit/ie.html

If the page supports Nav4 but not HTML 4.0/W3C DOM:
http://sites.netscape.net/ekrock/fixit/layer.html

If the page is breaking because of user agent detection problems:
http://sites.netscape.net/ekrock/fixit/useragent.html

(Use that one when a page doesn't work or has a JavaScript error because the client-side JavaScript isn't detecting the Navigator 5 Mozilla/5.0 userAgent string, or discover that a server-side CGI is returning the wrong page because it's not detecting the Mozilla/5.0 HTTP USER_AGENT string or is choking on its HTTP 1.1 CONTENT_TYPE string.)

Likewise, if you're examining a bug report in Bugzilla and realize it's caused by these issues, mark the bug INVALID. Then use the email creation templates to notify the bug reporter and the page owner of the need to upgrade. Bugs closed as INVALID in this way count half a point in the BugAThon!

Hint to avoid filing bogus bugs: if content on a page doesn't position correctly or there's a JavaScript error, do a View Source and look (or copy and paste and search in a text editor) for the strings document.all and layer (case insensitive). If you find those strings in the JavaScript or the HTML markup, think twice before filing a bug. Create a simplified test case without the proprietary features and see if the problems still occurs.


#10 Why are you complaining?

by Anon

Monday November 8th, 1999 7:09 PM

You are replying to this message

Webmasters have been upset ever since the 4.x browsers hit the market because to take advantage of new features they have to write pages twice basically one for Nav one for IE just because the same code does not work on both browsers.

Developers at Mozilla have been pounded with letters from the Web Standards group and even the outside contributors like myself have been helping them by checking the browsers ability to support standard based web pages.

In the end, I think this is great. At least everyone will be able to stop blaming Netscape for the Standard problems and start pointing their fingers in M$.