Weekend Discussion: Microsoft and 86%

Friday July 14th, 2000

There has been a lot of discussion about Microsoft's release of IE 5.5 recently, especially in regards to their support for standards such as CSS, DOM, and XML. Apparently Microsoft is developing new proprietary technologies at the expense of standards compliance in core web technologies.

The conversation in the WSP's mailing list has gotten overheated, and the WSP has released a piece on IE 5.5.

CNet is running an article on IE 5.5's proprietary new features, and there's a discussion on Slashdot regarding this very issue.

I now have a weblog at the O'Reilly Network, and you can check out my first piece, devoted to Microsoft's .NET initiative, which hits on Microsoft's standards support.

With all this hoopla aimed at Microsoft, we shouldn't be letting Netscape off easy. I think it's time for Netscape to come out and state clearly where they expect to be in terms of standards compliance at version 6.0. If it is not the 100% that we had been told to expect, it's in their best interest to say why. Remember, Netscape 6.0 will have its own "behavior" implementation (XBL) that is, at this point, just as proprietary as Microsoft's DHTML behaviors (the dev team plans on submitting XBL to the W3C in the future).

And although has not taken a position one way or another on Mozilla's standards compliance, it would be nice if they could weigh in and let the community know what they're thinking in terms of standards support in Mozilla's first release.

What do you think about standards support and compliance? Is it important? Or should the placation of existing customers be the priority? Let us know!

#87 Re: Forget about skinning!

by bertilow

Monday July 24th, 2000 6:55 AM

You are replying to this message

I'm mainly concerned with bug 26026, and the fact that it is being seriously considered not fixing it for the first release, which would mean less support for the current HTML recommendation than we already have in Netscape 4 and MSIE4/5. Lots of perfectly simple and correct pages would not be correctly handled. Actually the comment from ekrock on 2000-07-17 states that Mozilla need not support the current HTML standard fully at all! (Note that the current HTML recomendation is XHTML 1.0.)

There are also issues with XML declarations and encodings that has made valid XHTML pages not display at all, or display without UTF-8 support, but that might have been fixed by now.