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 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:
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!
#49 Upcoming API?
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?