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!
#23 Ugh, but...
Tuesday November 9th, 1999 5:18 AM
You are replying to this message
If support for broken DOM/HTML/old tags is included, then it *has* to come with some of "Bad HTML" (or whatever) indicator that other people have suggested (it was indeed the only useful thing that Arena had !).
Even better might be to allow the "Bad HTML" legend to be clicked on and a pro-forma fill-in form (Web URL, document title, standard "you are serving a page containing bad HTML" blurb, plus a space to put the Webmaster's e-mail address in) appears which can be used to send negative feedback to the offending Website.
That way, people can browse broken sites without taking a blind bit of notice of standards compliance, but those who care can easily put pressure on the Webmasters to get them fixed.
The "Bad HTML" indicator is a wonderful thing - not only does it pick up bad sites on your travels, but it acts as a syntax checker for your own Web pages too (so no more out-of-date Weblint or equivalent needs to be used to validate your pages).