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.

#5 WIll do nothing but IRRITATE webmasters

by Anon

Monday November 8th, 1999 5:20 PM

You are replying to this message

Come on, Mozilla isn't in in Alpha, and there is no browser that supports the DOM standard out there, and you guys are expecting webmasters, who already have their hands full supporting umteen browsers, to include a nonexistant one?

There is simply no reason for anyone to deploy a DOM version of a site at this time. Research prototypes? Yes. A DOM version of Yahoo or Amazon? A waste of time.

Atleast wait until some browsers EXIST that support the standard before you lobby people.

And if the Mozilla team was smart, they would support both NS DOM and IE DOM as switches. You can't just "rip and replace". If you want to move the net from prioritary standards to open ones, you need to provide a migration path.

A Mozilla that chokes on Netscape/IE enabled pages is a non-starter.