Web Standards Project Blasts IE
Monday April 10th, 2000
Luke writes, "The Web Standards Project posted a press release pointing out (and frowning upon) Internet Explorer 5.5's poor standards support. IE still does not fully support CSS1 or HTML 4, and has very poor support for DOM level 1 compared to Mozilla, which is currently very close to full support with only minor bugs left."
#4 Re: Who are you kidding??
by ttielkes <firstname.lastname@example.org>
Tuesday April 11th, 2000 5:20 PM
You are replying to this message
> Mozilla is not the tool for teh content provider, but for the user. The user *can* load/save/print a document in Mozilla, the content provider should not be able to do that IMO.
I wrote " *like* an editor without .. ".
You could also say that "XML support in Mozilla is like a browser without an address bar, back button or stop button"
>That attitute is exactly the reason for the imcompatibilities we have today. If the standards are not sufficient, you should enhance them /together with the other vendors/.
Wrong. Standards follow practice.
Nice fact for you: A W3C standard only becomes that when there are at least two different independant implementations. Standards are build on experience, on feedback, on getting your hands dirty with some technology.
The mess we have now is mostly (css & css positioning) because Nescape chose not to implement standards in Nav 4.5.
IE's pace of CSS implementation has me disappointed as well. On the other hand, IE5's HTML DOM is (to my experience) flawless.
The W3C DOM documents *explicitly state* that the implementor has to add meaningfull methods for loading/saving/serializing. Sun's XML parser is 100% compliant, but it also has methods for loading/saving/additional functionality.
I mean, what's the use of a parser if you can't load or save data?