W3C home > Mailing lists > Public > www-style@w3.org > July 2004

Re: [CSS21] Test Suite

From: Ian Hickson <ian@hixie.ch>
Date: Sat, 24 Jul 2004 11:36:11 +0000 (UTC)
To: Thomas Scholz <info@scholz-webdesign.de>
Cc: www-style@w3.org
Message-ID: <Pine.LNX.4.58.0407241034150.6726@dhalsim.dreamhost.com>

On Fri, 23 Jul 2004, Thomas Scholz wrote:
>>
>> You don't have to cope with lots of rendering modes. Just trigger
>> standards more. To do that, just make sure the first thing in the
>> document is an HTML4 Strict DOCTYPE.
>
> I can't. You too.
> <http://216.239.59.104/search?q=cache:Dg36FzGJF20J:ln.hixie.ch>

Actually that's a good example of the heuristic doing exactly what it was
designed to do.

The idea behind DOCTYPE-triggered rendering mode switching is to detect
legacy documents that were written expecting the rendering of old,
non-compliant UAs. How would _you_ do it? The requirements are that it be
determined before parsing begins (i.e. before the first element), and that
valid strict documents be rendered in strict mode and that legacy content
(cnn.com, microsoft.com, etc) be rendered in quirks mode.


> While I see the problem behind the idea of doctypeswitching, I really,
> really hate the solution. It never worked and it will never work.

Quite the contrary. It has issues, but it has worked better than every
other proposed solution could have.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Saturday, 24 July 2004 07:38:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:31 GMT