IE5 Released - Not HTML4, CSS1 or XML Compliant

Thursday March 18th, 1999

IE5 is out, and not only is it incompatible with CSS1, but it's DOM is faulty (and proprietary) and HTML4 support is incomplete. Also, it's XML Namespaces implementation is just plain wrong. It does poorly on the Import test, and renders the boxacidtest improperly (and badly).

On an interesting note, the article I linked to above was available this morning. Now, if you go to and find the same article (it has a new link), you'll find that all of the criticism regarding MS's standards compliance has been placed on a second page of the article. Look at the two links to see what I mean. Curious, no?

In response to criticism of their standards support, Microsoft's Mike Nichols said, "It's ironic that people are challenging our standards support when we have led by a substantial margin in this area since IE4". As I mentioned before, expect Microsoft to blame Netscape for Microsoft's lack of 100% standards compliance. The first person to point us to a new article that makes this claim (Microsoft already stated something similar months ago) will get a MozillaZine T-Shirt, when they come available. Our T-Shirts are still in the design phase, but we expect to have something soon.

Folks, stay calm. The Mozilla team is working hard to get a basic browser/mail-news reader into your hands that you can start using full-time. If you need standards compatibility, just go to our fetchBuilds section and download the latest build for your platform. You can see how the new browser, "apprunner", is shaping up, and try out your pages in the testbed viewer, undeniably the most standards compliant browser on the planet.

#50 Re:IE5 Released - Not HTML4, CSS1 or XML Compliant

by Mark Wilson

Sunday March 21st, 1999 12:53 AM

You are replying to this message

OSS is cool, it works and it is the way the truth and the life (artistic license).

BUT OSS without a good business focus is goingt o deliver the wrong product on time, on buget and on spec. But did you note the 'wrong product' part? The emphasis on the business vision is crucial and I re-iterate that the developers out there must be won over.

Just in case you didnt read my other post, here is an important two stanzas:

</importantstanza>You can put all you want into XML compliance. But at the end of the day, MS ships an XML IDE and guess what? Your compliance means diddly squat becoz you don't have an IDE which makes use of it, but they do and it make XML apps which are compliant to THEIR vision.

So, what are you giving developers so they will build to YOUR vision?<importantstanza/>