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 news.com 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.
#10 Re:IE5 Released - Not HTML4, CSS1 or XML Compliant
Thursday March 18th, 1999 6:45 PM
You are replying to this message
IE5 may not be compliant, but it sure is fast. It displays pages much faster than NS4.51, lays them out very quick, can scroll through complex pages rapidly and has much better cut and paste. It seems to layout pages and not require silly refreshes as often as NS on resize/refresh etc, which makes it even faster. (And still supports :hover from CSS2.. NS? hello?)
Mozilla has much work to do to catch up to this speed demon. Compliance is important, but the world keeps turning, and unless Mozilla has a product soon I don't see why people would want to wait with old technology rather than going with IE5. Very sad for me to say, but I am impressed with IE5 so far.
And if there are tags that work in IE but are not standard, I hope Mozilla can support them externally through an addon .dll or something "ieaddontags.dll" so we don't continually get left behind.
We can rant about non compliance, but 99.9% of the world just doesn't care.. they want things to work. IE5 is popular no matter how much you bash it from a technical standpoint (same for windows), so it is silly to beat your head against the wall. Better to put effort towards building a better product and _lead_ the pack rather than straggle behind condemning the leader. People will gravitate towards the better product. But a compliant product doesn't necessarily mean better. Again, 99.9% of the people just don't know or care.