W3C home > Mailing lists > Public > public-html@w3.org > April 2007

Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)

From: Alfonso Martínez de Lizarrondo <amla70@gmail.com>
Date: Thu, 19 Apr 2007 20:08:20 +0200
Message-ID: <af2a8eab0704191108k70e0eca0vd2acf9b4be3d1f2d@mail.gmail.com>
To: "Dão Gottwald" <dao@design-noir.de>
Cc: "Lachlan Hunt" <lachlan.hunt@lachy.id.au>, "Chris Wilson" <Chris.Wilson@microsoft.com>, public-html@w3.org

> 1.c We have _one_ more opt-in, namely <!DOCTYPE html>, and MS doesn't
> officially support it until the standards compliance is reasonable.

So you say that MS shouldn't release new bugfixes related to standards
rendering "until the standards compliance is reasonable"?

What's reasonable?

How can you check that everything that you want is fixed if they don't
release new versions?

I would expect the new bugfixes to uncover more problems that until
now they weren't important because other things were so broken that
nobody tried to use them that way, and of course there are regressions
to be expected if only MS test their browser.

Chris is saying that they plan to use <!DOCTYPE html> to trigger the
new standards mode, but only MS knows how many fixes they plan to add
in that mode, and by the way that he talks he seems to acknowledge
that not all the bugs will be fixed in the next version, so they want
to have a way to differentiate future rendering modes.

I don't like the idea of having to deal as a web author with several
IE engines at the same time, so I would like to have a way to be sure
that future IEs don't break my pages, and when the percentage of users
of the new version is high enough then embrace the new rendering modes
for pages that I care and develop.
Received on Thursday, 19 April 2007 18:08:24 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:19 UTC