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.

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

by Kovu <>

Thursday March 18th, 1999 10:27 PM

You are replying to this message

One major MS tactic is that by allowing customers to change the MS icon in the upper right, they hope to head off open source. By allowing portals like Altavista etc. to give their versions of IE customized, they are hoping to make IE the standard in the market by the time NS 5.0 comes out. They are aware AOL 5.0 is going to lose 16 million customers for them, are well aware that NS 5.0 is going to be ridiculously compliant and portable to just about everything, and are trying to head the market off at the pass now before it's too late for them. Likely they saw the window coming and snuffed compliance in favor of getting the product out first, giving them at least six months of market saturation. Hopefully, the fact that IE code is still proprietary and closed will make this not matter much in the end.

Hail Mozillans, to your computers, and help prevent this potential catastrophy!

Actually, I'm not too worried. AOL has mucho cash and NS (the deal wound up costing like 9.8 bil!) is worth a great deal of money to them. The last thing they want to see is IE 5 become standard, and will be infusing significant funding into making sure this does not happen. Have faith, and sleep little!