Re: Version information

>
>
> And that is our plan, except I think perhaps our definitions of "too
> extreme" differ.  We can't, for example, change the behavior of how we
> support CSS floats in IE7 without requiring an opt-in, since we would change
> layout significantly for half the web.*  When we break the web, it's our
> fault, even when we're breaking it to improve standards compliance.
>
> We (Microsoft) want to and plan to continue to bring our implementation in
> ever-higher compliance with the standards.  We can't change our behavior for
> content that exists today, though, so we will have to have content
> developers opt in.  I'd like to know when someone is creating HTML 5
> content, because (just like Quirks mode) that tells me when the last time
> they looked at the standards was.  Same with HTML 6, etc.



But imagine for a moment that this group didn't exist and no HTML 5 will
ever be published.

You have just stated that Microsoft want to improve the compliance with the
standards, that means HTML 4.01 and CSS2, fixing the bugs in those
implementations shouldn't require a new version of HTML or CSS. Web authors
will need a way to use the new fixes and leave the old workarounds like
legacy content, but the opt-in method doesn't has to be a version
information header in the HTML, because after all they'll be addressing
differences in the rendering of the same standard between two versions of
the same browser, and the web authors can't state that they want the HTML 5
rendering mode because as I said this group doesn't exist.

There must be another way to trigger the really-really standards mode in
IE7+ (and in the more distant future make that the default standards mode)

Regards