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!
#1 Does this mean Mozilla will not support these?
Monday November 8th, 1999 2:57 PM
Most sites have support for both IE5 and Communicator 4. Rather than breaking these wouldn't it be better to choose either IE5 or Comm4 and support that for backword compatibility?
#2 Reporting DOM Bugs? Be Sure to Read This!
Monday November 8th, 1999 3:24 PM
This is a dangerous decision to not support the NS 4.0 DOM. It'll mean that people switching to Mozilla (next March?) won't be able to use any dynamic HTML sites initially.
It'll also leave a bitter taste in the mouths of the developers who invested the time in learning and using the NS 4.0 DOM.
#4 Reporting DOM Bugs? Be Sure to Read This!
Monday November 8th, 1999 4:13 PM
They're accepting patches...
This important link was missing from the article even though it was in the original message in the layout newsgroup.
Basically, implenting some of the old 4.x DOM would break standard compliant DOM due to tags with duplicate meanings. I am sure this is not the case all around. There was a discussion on all of this a few months ago and the bottom line is that the propriatary DOM is out and W3C DOM is in.
Here is Eric's before you email me link:
#5 WIll do nothing but IRRITATE webmasters
Monday November 8th, 1999 5:20 PM
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.
This is probably the worst piece of advice I've heard from a professional developer.
If the pages don't display correctly in Mozilla, but they do in IE5, N4, that is a Mozilla problem - not the webmasters.
*Users do not care if this breaks your standards compliance.*
Could you be anymore short sighted? Just because most users are ignorant to what goes on behind the scenes, it doesn't mean we need to follow their lead. The PROBLEM is the uneducated webmasters who deviated from the standard in the first place.
Plus, the sites may not totally break. It'll just be the sections where the web developer copped to the proprietary route. :)
#53 Re: <slap>
by queenmariam <email@example.com>
Saturday January 21st, 2006 2:48 AM
THIS LETTER IS WRITTEN IN FRENCH AND ENGLISH. CETTE LETTRE EST ECRITE EN FRANÇAIS ET l'anglais. From: Miss Mariam Mustapha Abidjan, Cote D'Ivoire. +225 07725768 Email: <firstname.lastname@example.org>
REQUEST TO BE MY GUARDIAN AND THEN HELP ME THUS:
Good day and how are you today? I hope fine. Please permit me to inform you of my desire of asking you to be a guardian or foster parent to me and then help me out in what i am about to tell you. My name is Miss Mariam Mustapha (23). I am the only child of Late Mr. & Mrs. Ahmed Mustapha. My father was a very wealthy cocoa merchant here in Abidjan, the economic capital of Cote D'Ivoire. He was poisoned to death by his business associates on one of their outings on a business trip. My mother died when I where baby. Before the death of my father in a private hospital here in Abidjan, he secretly called me by his bed side and told me that he has the sum of Ten million five hundred thousand United State Dollars USD ($10.500,000) deposited in a suspense account in one of the big banks here in Abidjan. He told me that he used my name (Mariam Mustapha) as the next of Kin in depositing the money.
He then strongly advised me not to seek for assistance in the investment of the money from his lawyer nor any of his friend here but to seek for a foreign partner from a country of my choice (outside our country, Cote D'Ivoire) that will assist me in the wise investment of the money. I have since left the money in the bank with the view of my making use of it for investment purposes after my education carrier here. But as you may be already aware by now, our country (Cote D’Ivoire) is presently at political crises. Rebels have already taken over the whole Northern part of the country and making efforts towards the capture of the commercial centre of the country, Abidjan, where i am now.
For this ugly development in this country, i have now decided to take quick actions and have this money transferred out of this country before it is too late to do that. I now want to transfer it out and use it for investment purpose like real estate management or hotel management. Because of this i am honourably seeking your assistance in the following ways:
(1) To serve as a guardian to me and then assist me transfer the money into your bank account. (2) To make arrangement for me to come over to your country to further my education and then settle there permanently.
If you accept to stand as my guardian or foster parent to me, i need not discuss on any percentage with you as you have to see the whole money as yours and then assist me invest it. But if you still want a percentage, I am willing to offer you 20 % of the total money as compensation for your assistance. Please tell me if you feel the percentage I offered is not ok by you.
As soon as I receive your concrete assurance to assist me with my proposal and also your full contact address/phone number, I will then give the bank your contact information and then tell them to transfer the money into your account as I want to come over to stay with you permanently. The bank will then contact you and communicate with you on the transfer. You shall then be giving me information on when the transfer will be over. I will also send my pictures to you and shall also need yours too.
No matter what your decision may turn out to be, please I beg you to keep this highly secret for my safety, as I believe that those that killed my Daddy are still after me. Please reply me through this my more private and confidential email box: <email@example.com> Thanks and God bless you.
Best regards, Miss Mariam Mustapha. +225 07725768 <firstname.lastname@example.org>
Mon cher Permettez-moi de vous informer de mon désir de l'entrée dans le rapport d'affaires avec vous. Je suis Mustapha Mariam la seule fille du défunt pare Mustapha. Mon père était un négociant très riche de cacao à Abidjan, la capitale économique de la Côte d'Ivoire, mon père a été empoisonné et tue par ses associés d'affaires sur l, une de leurs promenades en voyage d'affaires. Ma mère est morte quand j'étais un bébé et depuis lors mon père m'a pris si spécial. Avant la mort de mon père en octobre 2002 dans un hôpital privé ici à Abidjan il m a secrètement appelé de son côté et m'a indiqué qu'il a la somme de US$10.5M (dix millions cinq cent mille, les dollars d’etats-unis) unis d'état sont partis dans le compte d'ordre fixe/ordre dans une banque principale ici à Abidjan,. c,est lui qui a employé mon nom en tant que sa seule fille pour le prochain des parents en déposant des fonds. il m, a également expliqué que c'était en raison de cette richesse qu'il a été empoisonné par ses associes d'affaires. Que je devrais chercher un associé étranger dans un pays de mon choix où je transférerais cet argent et l'emploierai pour le but d'investissement tel que la gestion de biens immobiliers ou la gestion d'hôtel. Cher, je cherche honorablement votre aide des manières suivantes: (1) pour fournir un compte bancaire dans lequel on transférerait cet argent. (2) pour servir de gardien de ces fonds puisque j,ai seulement 23 ans. (3) pour faire l'arrangement pour que je vienne dans votre pays pour mon éducation et pour fixe une autorisation de résidence dans votre pays. D'ailleurs, cher, je suis disposé à vous offrir 20% de toute la somme comme compensation pour votre effort/entrée après le transfert réussi de ces fonds en votre compte nommé outre-mer. En outre, vous indiquez vos options pour m'aider pendant que je crois que cette transaction serait conclue dans quatorze (14) jours où vous signifiez l'intérêt de m'aider. Prévoir à avoir de vos nouvelles bientôt. Merci que Dieu vous bénisse Les meilleurs souvenirs Miss Mariam Mustapha +225 07725768 <Mariamwatch2@yahoo.com>
#7 Reporting DOM Bugs? Be Sure to Read This!
Monday November 8th, 1999 6:42 PM
This is a very gutsy move. Or an incredibly stupid one.
What drives standards? Software. The W3C could write paper standards until the cows come home, but it wouldn't make a bit of difference if those standards were not supported in a working browser used by a lot of people.
But it's that last bit that makes the difference. How many users are using Mozilla NOW? Why would a webmaster care about a product that isn't even in beta yet?
If MSIE had not supported standards, Netscape would have forced JCSS down our throats (as they did with CENTER even though DIV was already decided upon) and few web pages would be using standards-based CSS. Mozilla's impact on the web (and MSIE) will be determined by it's timeliness and it's popularity.
As for current web pages, there are actually very few that use the DOM. It's so complicated, and it works so differently in each web browser that most people have just stuck to HTML for the basics and used Flash or Java for the interactive stuff.
Back in old days, Arena, the W3C's old web test bed, would flash a "bad html" message in the upper-right-hand corner if it was used to view a page with bad html. Several people suggested that Mozilla do this in the "Dave Whitinger on Mozilla's Importance" thread. I think it would be an even better idea now that Mozilla requires more strict HTML compliance.
Besides, when users actually know when web pages are non-compliant, webmasters will care enough to write compliant web pages. Who wants a customer to see "Bad HTML?"
I think thats a gread idea. However, a 'compatibility' mode would also not hurt :)
#51 Reporting DOM Bugs? Be Sure to Read This!
Wednesday November 17th, 1999 1:54 AM
One of my work computers came with Internet Explorer 5.0 preinstalled, but no Netscape or Mozilla. I went to a couple of websites and got alerted by IE5 (via a modal dialog box, of course) that the page I was about to see had "bad HTML," and the entire time I was at the site, the little piece of paper with the blue E on it was replaced with a little piece of paper with a yellow triangle alert icon on it, and the words, "Done, but with errors on page."
#52 Oops. Title should've been "IE5 already does
Wednesday November 17th, 1999 1:57 AM
Oops. Title should've been "IE5 already does that"
This is what most of us wanted. Kill all the non standard code!!!!!!!!!!
Actually, now that I got your attention, from what I have been seeing this past year, Mozilla developers have been putting lots of work into parity with the 4.x browser. I think they just ran into problems with certain outdated functions and like they should decided to go with the spec rather than support the non standard method.
It looks as if (and I would not hold your breath) that IE 5 Mac will probably be more standards compliant. So, who knows how things will work out.
Webmasters have been upset ever since the 4.x browsers hit the market because to take advantage of new features they have to write pages twice basically one for Nav one for IE just because the same code does not work on both browsers.
Developers at Mozilla have been pounded with letters from the Web Standards group and even the outside contributors like myself have been helping them by checking the browsers ability to support standard based web pages.
In the end, I think this is great. At least everyone will be able to stop blaming Netscape for the Standard problems and start pointing their fingers in M$.
You know, Netscape and Microsoft are members of the World Wide Web Consortium and as such signed off on the standards their browsers fail to implement.
I think this change is Netscape and the Mozilla.org's way of trying to live up to the commitment they made as memebers of that organization to implement its non propriatary standards.
#12 Time for standards
Monday November 8th, 1999 7:20 PM
The reason why we have new versions of web browsers is so people can upgrade.
Supporting only standard DOM will be another reason for people to upgrade to Moz.
#13 Reporting DOM Bugs? Be Sure to Read This!
Monday November 8th, 1999 7:41 PM
This is ridiculous. IE 4/5 have like 60-80% (depending on who you believe) market share. By not supporting the dominant player it will reduce the time it will take for NS 5 to gain market share. Embrace and extend stupid! :-)
#14 Reporting DOM Bugs? Be Sure to Read This!
Monday November 8th, 1999 7:45 PM
This is ridiculous. IE 4/5 have like 60-80% (depending on who you believe) market share. By not supporting the dominant player it will reduce the time it will take for NS 5 to gain market share. Embrace and extend stupid! :-)
#15 Reporting DOM Bugs? Be Sure to Read This!
Monday November 8th, 1999 7:52 PM
And it will remain small, and fast to download and install. And it will be fast to cruise creative and demanding sites. It is a win-win situation for webmasters and Mozilla developpers.
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.
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."
"another one won't hurt them?"
Get real. Why should developers support DOM *NOW* when no browsers xeist that can handle DOM. There is ZERO, absolutely, ZERO demand from users for ths.
Mozilla can support all the "standards" it likes, but it will be speaking Esperanto while the rest of the world will be speaking English.
It *better* support backwards compatible broken DOM/HTML/old tags, otherwise it is doomed.
Given the information already in public domain, I doubt I have any chance of convincing you of the Way Things Are if you have not figured them out already, so I'll just concede defeat.
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).
Currently I'm designing all of my pages to work in Mozilla and the I load them in Nav4/IE to see if they display everything (I don't really care what they look like. IE is close some of the time. Nav - well... it displays it). I do this because what I type in actually shows up in the Mozilla Daily Builds as I expect it.
Its just so much easier to get the page to display properly.
#25 has the web become so conservative already ?
Tuesday November 9th, 1999 7:18 AM
the web is a rather young technology, but people like you seem to be conservative as if it was dozens of years old... i'm disappointed and worried about such a behaviour. is innovation already dead on the net ?
#30 has the web become so conservative already ?
Tuesday November 9th, 1999 1:27 PM
Fortunately, I don't think what we have here is indicative of all web developers.
Developers, let your DOM version serve as an IE5 version (avoid IE idiosyncracies where possible, and if need be make a few tweaks when Mozilla is released) until Mozilla is released. Then its both an IE5 and Mozilla version, and everyone else can get vanilla.
Have you developed for the Netscape 4 DOM? It's not pretty and has some annoying quirks. I have no reservations saying that I much prefer IE 4's approach to DHTML over Netscape 4's. I've spent many painful hours working with Netscape 4 and I'd not wish that on anyone (there *is* some logic behind the implementation, but it can be rather inconsistent).
At the moment the best way support IE4/5 and Netscape 4 at the same time is to use a crossbrowser API (Dan Steinman's DynLayer is well known) and I've developed my own one to support the work I do (we are writing a servlet-based application that has a full DHTML interface - pull down menus and the like). As my API evolves I intend to support IE4, NN4 and DOM1 (which should work in IE5 and Moz) and to make the API available for anyone to use. The biggest limiting factor will be Navigator 4 because it supports fewer CSS properties and provides relatively limited access to all the objects on a page.
The DOM approach - explicitly adding nodes to a tree - is somewhat different to the approach used in version 4 browsers so I anticipate current crossbrowser APIs will have to evolve a little... but an anticpiate many of them will be ready by the time Mozilla is released as Navigator 5. In a few years time we should see DOM Level 1 compliant browsers having 80+% market share and the need for these crossbrowser APIs will start to disappear thanks to the wonder of standards compliance.
I support the move of the Mozilla team to break with the past and not implement support for older DHTML because the DOM1-based approach is much more theoretically sound and offers more features to the developer.
XUL should also give Mozilla an advantage for organisations planning to implement intranet applications.
Yes, right through 1998 I was designing dynamic elements for websites of mine initially for N4.x, and later for both N4.x and IE, so I understand as well as the next person the pain involved in doing something as fundamental as an expanding menu ;)
You raise good points, and I'm sure Mr Steinman will update his script with W3C DOM support (if he has not done so already). I think there should be some sort of stamp that a browser has that identifies it as fully <x standard> compliant so scripts can check ;)
What someone might like to do is develop emulation functions, e.g. create a function that searches through a document for an element with a specific ID (scanning through each level of layer in NN4.x, for instance, and each element in the all collection in IE4) and return the object. What you'd then do is attach this function to document with prototype:
document.prototype.getElementById = myGetElement;
You could then bundle this into a JS file. The function would be run on non-Mozilla/IE5 browsers (using the Devedge browser sniffer, say) which would emulate the appropriate function. This has been done the other way too, someone wrote a function a while back for Mozilla that imitated IE's innerHTML attribute.
Neither am I against the implementation of native code to do this, my point to the "doom and gloom" posters is that time does not permit the implementation of workarounds that may cause problems with the code most web developers want. I'm sure mozilla.org would welcome an implementation of this if someone provided the code.
#17 Reporting DOM Bugs? Be Sure to Read This!
by danielhill <email@example.com>
Monday November 8th, 1999 9:40 PM
The dude who mentioned the "Bad HTML" thing is the man. I FULLY agree with that proposal. MS and webmasters need to be taught a lesson. Do what the spec says or get BURNED!!!!!! HAHAHAHAHAHA!!!!
#21 Reporting DOM Bugs? Be Sure to Read This!
Tuesday November 9th, 1999 12:11 AM
BTW, IE4/5 are much better at support of these standards, then say NN4.x. So I think not MS should be taught a lesson but Netscape, which finally got it right.
#19 Demand www.zdnet.com is FIXED!!!
Monday November 8th, 1999 11:20 PM
<http://www.zdnet.com> is a primary candidate for fixing to use with Mozilla.
I suggest everyone use this page:
to send a message to:
Your button onSubmit DOES NOT DO ANYTHING!
How silly is that? I guess your script to detect user agents does not itself work correctly?
God, Netscape sucks.
#26 Whatchew talkin' 'bout, Willis?
Tuesday November 9th, 1999 7:52 AM
er... could you be a bit more specific ?)
"We are going to break compatibility with all previous products. It is the user's problem." This kind of thing is exactly what's turned me off of Java. And remember Commodore? Others' suggestion to support a wider range of (non-)standards is good. Get that "Bad HTML" light blinking, sure, but make the browser useful on pages that work for NS 4.x and MSIE. If you don't, Mozilla will just become "that screwed-up browser that shows pages wrong."
Redefining some browser bugs as flaws in others' HTML will knock the bug count down, making it more likely that the project can go into open beta testing sooner.
#31 Reporting DOM Bugs? Be Sure to Read This!
Tuesday November 9th, 1999 5:27 PM
It'd not be too hard to wrap WC3 DOM into a document.layers type of thing, would it? Creating objects, that sort of thing...
Even if it was dog slow, it'd work, and still would be DOM based. Keeps page compatibility
#33 Reporting DOM Bugs? Be Sure to Read This!
Tuesday November 9th, 1999 5:41 PM
Actually, it isnt that easy. Netscape 4.x and IE4/5 both uses tags that are in standards, but do non-standard things. There is no easy way to support the legacy code in Netscape without breaking the good code in Mozilla.
#37 Stop supporting the best HTML tags?
Tuesday November 9th, 1999 8:04 PM
#48 Stop supporting the best HTML tags?
Wednesday November 10th, 1999 6:49 PM
Lists your alternatives.
Its not that support was not wanted. The problem was that to implement the standards many of the tags mentioned in the standard were implemented in a propriatary way that is not in compliance with the standard.
The developers have taken lots of fack from webmasters for propriatary tags and have decided that if a propriatary extion breaks a standards extension, that the propriatary goes.
#39 Reporting DOM Bugs? Be Sure to Read This!
Tuesday November 9th, 1999 8:39 PM
Here's some news for ya to nibble on:
I guess ol' Jessy doesn't think much of Netscape & Co.
#40 'Bersting' out with laughter
Tuesday November 9th, 1999 9:10 PM
I just finished reading the article and thought it was funny. . .sort of.
Jesse spent so time reaching his conclusion that Netscape is dead & buried and that IE has now won the browser war, towards the end of the article he then tossed in a mention of the upcoming Navigator 5 being released as if it were an afterthought. I mean, if you're on that much of a negative roll then why bother? I expected as much, I guess.
#41 Reporting DOM Bugs? Be Sure to Read This!
Tuesday November 9th, 1999 9:20 PM
When he writes uninformed tripe like that (no support for XML? Nice to see his head is still firmly embedded between his cheeks [and I don't mean the ones on his face]), it's small wonder most of us don't think much of him.
That was even less informed than the average C|net/ZDnet article.
#43 it's clearly "disinformation" !
Wednesday November 10th, 1999 2:35 AM
it's just another step in the info-war.
Your story is inaccurate. The browser war is far from over.
2. Giving over Java development to Sun is a good thing. It means Netscape will always have the latest version of Java integrated. Netscape has an "Open Java Interface" and users can plug in any Java Virtual Machine they want. As Sun releases each new Java version, users can download it and plug it straight into Netscape 5 (something Microsoft IE can't do).
3. AOL hasn't made Netscape their official browser, yet. I guess we will have to wait until Netscape 5 is released and see what happens.
5. It is good that Netscape has opened its source code to the outside world. Everyone but Microsoft will be the better for it. Users will especially benefit because they will gain a browser with far fewer bugs (due to the widespread scrutiny of the program by people outside Netscape), and with extra features written by non-Netscape developers.
Netscape may have trouble regaining its market share by the time Netscape 5 is released, but it certainly won't be because Netscape 5 is technically inferior. Microsoft has a huge advantage in the market share war by forcing IE onto all Windows user's desktops by bundling it with Windows. Microsoft has needed to use these and other (probably) illegal practices to gain market share from Netscape.
I don't think it is clever to scream about Netscape's imminent demise just because 60% of companies recently choose IE over Netscape. It wasn't all that long ago that these statistics were reversed. Things change very quickly in the computer industry. Netscape will soon have a browser which matches and in many ways will be superior to IE. Netscape is still the most popular browser on Linux, and as the open source development community snowballs behind Netscape, we will see an acceleration of Netscape's browser development. We still don't know what will happen as a result of the Microsoft anti-trust trial, and the results of this may too have a substantial benefit for the ability of Netscape to regain it's lost market share. Netscape is far from dead. The newly rewritten code, and a growing community of outside developers will give Netscape the edge over Microsoft in the coming years as it seeks to regain what has recently been lost.
Please spend more time to write a more accurate story next time.
#45 Reporting DOM Bugs? Be Sure to Read This!
by kalperin <firstname.lastname@example.org>
Wednesday November 10th, 1999 9:04 AM
AS a web developer I feel everyone's cross-browser pain. I consider the holy grail of standards complience important enough to re-write all of my pages from scratch if I have to. Perhaps someone with more experience using Moz can point us to a primer in migrating from older proprietary systems to newer standards. What methods, properties or even tags will break? What common tricks will no longer work? What are some easy to use work-arounds for these problems? I imagine that this sort of document does not yet exist. Anyone with more experience than I with the new standards care to write one? I'd be happy to lend my assistance in any way that I can.
#47 Reporting DOM Bugs? Be Sure to Read This!
Wednesday November 10th, 1999 6:45 PM
Has the answer you are looking for.
But, to write a standard page, just use the validator at the w3c to point out what code is not valid.
Netscape 5 and Mozilla 5 will support the same non-standard code the 4.x browsers supported. That is unless, like in the case of the DOM's, that backwards support breaks the standards support.
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?
As far as I can tell, the problem here is not that proprietary pages will break in Moz. After all, it is actually the BROWSERS which are broken.. every proprietary tag on every proprietary page is nothing more than a bug workaround. The problem is that users, being stupid (spare me the PC rhetoric, it's true and you all know it), will immediately blame the browser for the failures of the page. And indeed, who DOESN'T cuss at the TV when the cable goes out, hmm?
This isn't a good enough reason to support all of the cruft that's out there, though, IMO. Mozilla has dispensed with all of the old proprietary code on the inside, and is far superior to anything else as a result.. let's finish the job and clean up the code on the outside as well.
I think that the "Bad HTML" warning would be an excellent idea even if it didn't double as a validator. I might even take it one step further and add an error dialog which briefly explains that the page is broken, forcing the users to recognize (if not necessarily understand) why pages seem to break and whose fault it is. (I envision the dialog as having a "Don't Show Again" and a "Tell Me More" button. The function of the first should be obvious; the second could dismiss the dialog and open a local file which briefly explains how broken pages came to be and why standards compliance is important.)
As for designers and acceptance... Having worked with both Mozilla and N4, I can confidently say that anyone who wants to keep the old code is insane, as well as a masochist. The "new" code is not terribly difficult to pick up, and few things compare to being able to get a piece of code right on the first try with little or no experience, only references. I have little doubt that anyone who gives it a try will quickly see the shameful folly of their past and adopt the standards wherever possible.. and lest any of you forget, it is the designers, not the users, who shape the growth and evolution of the web. Where we lead, they WILL follow.. they have no choice.