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.

#16 Ugh

by Ben_Goodger

Monday November 8th, 1999 8:19 PM

You are replying to this message

Mozilla supports STANDARDS. It is under no obligation to support the proprietary crap introduced by any of the other browsers in the past. Only the incredibly dull minded web masters will be irritated by this, as it was at the request of a huge number of developers that Mozilla went down this road in the first place.

Extending a site to support legitimate standards is a wise move. Why? Well, IE supports a fair bit of DOM/CSS stuff, so for many people, a DOM version might also double for an IE5 version. And if IE5Mac's "standards compliant" Tasman makes it into IE6Win32, developing DOM compliant pages will be developing for Mozilla/Communicator AND IE.

Furthermore, developers have been developing multiple versions/compatible versions of their javascript for ages now. Another one won't hurt them, especially not when they find out what a joy it is to program with DOM. Besides, no serious website uses DHTML for anything more than eye candy, given that a lot of people still use Netscape 3.0. Hopefully what they'll do is ditch their 4.x versions altogether, and provide plain content for all "old browser" users, providing dynamic content only to IE5/Mozilla/Communicator 5.0 users. This way scripting is a whole lot easier, and given the marketing impetus behind IE5 and the projected marketing behind future Mozillae, this seems like a good plan.

In other words, its not going to be hard. If you still think it will be, either pull the Classic tree and finish that yourself, or build IE/NN4 emulation into Seamonkey.

"We are not those who are frightened by change."