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?

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

by Ray Cromwell <>

Friday November 6th, 1998 11:24 PM

You are replying to this message

First of all, while XSL is still a draft, the current form of the draft is likely to make it intact into the final standard. Why not atleast have an implementation TRACK the standard? There are two Java XSL processors out there in addition to the Microsoft one. I wrote an XSL editor myself (presented at XML98) and was bitten when they changed the draft drastically, but I feel you should still track the standard (and DOM), instead of waiting to get caught with your pants down.

You should ship support for standards early and often if you want to beat MS.

Oh, and what about VML? Sure, it's a dead W3C standard, but I feel is it definately superior to PGML because it fits perfectly into the CSS box-model.

With VML, or a VML like language, it's trivial to support VML rendering in a browser compared with PGML. VML will "flow" correctly with HTML/CSS.

But why should Netscape support VML? Because VML, no matter what the W3C thinks, will be used in Office 2000.

Office 2000 saves MS Word documents as pure HTML + CSS with VML used for diagrams. It doesn't matter if VML isn't a W3C standard, soon all office documents, spreeedsheets, and presentations will use it. It's best if Mozilla will be able to view Office documents inline, otherwise people will use IE5 to do so.

I see another war brewing with Action Style Sheets vs Behavior Style Sheets. IMHO, neither is really technically superior to the other, and it doesn't matter much which one gets adopted, so why not get together with MS, resolve whatever issues bother you, an both implement a compatible language?