The New IE5 Feature Set...

Wednesday November 4th, 1998

George Giannukos writes in, "This article [a CNet article at Netscape's TechNews site] lists many of the new features that will be in IE5. Some very interesting ones I must say."

Sounds like MS is taking some moves from the Mozilla playbook. Who wants to place a wager on which group's solutions are more proprietary?

Also, maybe someone can answer a question for me. Why is it that whenever CNet does an article about Netscape, they always seem to have a MS spin doctor's words to finish out the article? Why does this article have no spin from the Netscape camp?

#5 Re:The New IE5 Feature Set...

by Ray Cromwell <>

Wednesday November 4th, 1998 6:14 PM

You are replying to this message

Ok, I love Mozilla, I love open standards, and I love Netscape, but you have to hand to Microsoft.

First off, IE4 has had NGLayout features for a long time (incremental layout/reflow, CSS, DOM, etc).

IE5 comes built in with the ability to display XML, XSL, CSS, VML, and handle standards no one else cares about like OSD.

VML is pretty cool, I must say.

Anyway, the biggest improvement of IE5 is their setup/install utility. IMHO, it is *WAY* better than Netscape. First of all, you can pretty much pick and choose which modules you want at a very fine grained level. But the best thing is that it automatically finds the fastest download site, an will hop between download sites doing auto-resume whenever the connections get stuck.

I have never used IE as my browser exception to check my web pages for compatibility. However, I think it is wrong to blindly attack Microsoft and praise open-source as a panacea. Both IE4 and IE5 have some good ideas, and support more web standards than the current communicator 4.5.

I can only hope that Mozilla5 will feature support for more Web standards than IE5 (CSS2, DOM, XML, XSL, SMIL, MathML, VML, etc) and support them comprehensively enough so that developers are not avoiding CSS and DOM features because of implementation bugs.

(like if the box layout model doesn't conform the same in IE5 and Mozilla5, developers will probably avoid the features that don't work, or worse, have to detect them on the server side)