On 04/02/2002 at 18:28 JTK wrote: >DeMoN LaG wrote: <delenda est> >> A proprietary Netscape >> 4.x DOM that includes Document.layers, a proprietary IE DOM that >> includes document.all, and a W3C complient one that Mozilla implements. >> The problem is NONE of the browser support all 3. All of them, however,
>> should work with the W3C complient one. > >No, Mozilla should render all existing web pages as well or better than >all existing web browsers. If that means it has to know what a >"document.all" is, tough noogs. Backwards compatibility is one of the reasons that Microsoft is having such a hard time supporting CSS over and above CSS1. Its also non-trivial to support two different object models of a document. It would be slightly easier to support layers but the decision was taken not to support it (which doesn't mean someone couldn't support it if they feel like coding it), so that the proprietary DOM wouldn't be perpetuated. If you want Mozilla to have a particular performance aim then I'd agree that it should render all existing valid documents, where valid is the set of documents conforming to W3C. > >> If people didn't do dumb things >> like go "I'm lazy, I'll just use Frontpage and not bother learning how >> to do my own code", > >God. I suppose you want me to code on punch cards too, huh? Mr. LaG: >IT'S 2002. WEB PAGES ARE NOT "CODE". WRITING HTML BY HAND DOES NOT >MAKE YOU A "PROGRAMMER". A great many WYSIWYG tools create invalid HTML code, I wouldn't blame the users for that I would blame the tool developers. Though, software in general might be of a much higher quality of some of those writing it had had the experience of using punch card. > >> you get crappy pages that don't work in some browers > >No Ace, just Mozilla. Try pointing IE 2 and 3 at a great many pages, try getting Opera to run some Javascript. Given the random quality of so many web pages its not surprising so many fail for people with a variety of browsers. S
