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

Re: [CSS21] Test Suite

From: Chris Lilley <chris@w3.org>
Date: Fri, 23 Jul 2004 17:06:46 +0200
Message-ID: <1039143368.20040723170646@w3.org>
To: Ian Hickson <ian@hixie.ch>
Cc: Thomas Scholz <info@scholz-webdesign.de>, www-style@w3.org

On Friday, July 23, 2004, 2:57:52 PM, Ian wrote:


IH> On Fri, 23 Jul 2004, Thomas Scholz wrote:
>>
>> It's up to the browser developers to render perfect valid HTML documents
>> according to the specifications. »Quirks« and »Standard compliance mode«
>> are moving targets, so I don't care anymore about the reasons for a bug.

IH> Actually they're pretty stable now.

Do they have actual documentation?

>> A bug is a bug is a bug. That's all I want to know. If tests had to
>> handle all the various different kinds of -- ahem --rendering modes,
>> they would become ridiculously complicated...

IH> You don't have to cope with lots of rendering modes. Just trigger
IH> standards more. To do that, just make sure the first thing in the document
IH> is an HTML4 Strict DOCTYPE.

Even if you don't conform to it. Its a flag, not a DOCTYPE. Apparently.

This becomes more of a problem when the XHTML DOCTYPES are used a s
flags - using a different one, which is perfectly legal, might or might
not trigger quirks mode.

Is there a list of these triggers? Per browser/os/version, obviously, I
don't imagine a single trigger works the same in all of them.



-- 
 Chris Lilley                    mailto:chris@w3.org
 Chair, W3C SVG Working Group
 Member, W3C Technical Architecture Group
Received on Friday, 23 July 2004 11:06:46 GMT

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