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.

#49 Upcoming API?

by Anon

Thursday November 11th, 1999 6:40 AM

You are replying to this message

I'm glad you pointed me to this page, since I've been looking for a guide to the practicalities of DOM use in NS5 - I've read the W3C documentation, but like plenty of webmasters this sort of thing measn little to me, what i needed was a guide to how I can refer to elements etc that I ahd discovered were screwed by Gecko when I checked out my own pages. Now I have it, sort of. I'm all for standards implementation, by the way, but in order to ensure that there are at least a few sites out there that can use the standards by the time the new browser is finally released, there is a need for more in the way of cross-browser coding guidance. A start might be updating the API library linked by Krock from the cross-browser DHTML technote at <http://developer.netscape…html/csspapi/csspapi.html> (when he gets a chance...) The whole thing needs a new browser branch for compliant browsers. A resource like that could stop a lot of complaining from people like me. Any chance of that?