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:

If the page supports Nav4 but not HTML 4.0/W3C DOM:

If the page is breaking because of user agent detection problems:

(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.

#7 Reporting DOM Bugs? Be Sure to Read This!

by Anon

Monday November 8th, 1999 6:42 PM

You are replying to this message

This is a very gutsy move. Or an incredibly stupid one.

What drives standards? Software. The W3C could write paper standards until the cows come home, but it wouldn't make a bit of difference if those standards were not supported in a working browser used by a lot of people.

But it's that last bit that makes the difference. How many users are using Mozilla NOW? Why would a webmaster care about a product that isn't even in beta yet?

If MSIE had not supported standards, Netscape would have forced JCSS down our throats (as they did with CENTER even though DIV was already decided upon) and few web pages would be using standards-based CSS. Mozilla's impact on the web (and MSIE) will be determined by it's timeliness and it's popularity.

As for current web pages, there are actually very few that use the DOM. It's so complicated, and it works so differently in each web browser that most people have just stuck to HTML for the basics and used Flash or Java for the interactive stuff.