W3C home > Mailing lists > Public > public-html@w3.org > February 2010

Re: Legacy Doctype and Doctype Versioning

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Wed, 17 Feb 2010 14:30:33 +0100
To: Maciej Stachowiak <mjs@apple.com>
Cc: Philip Taylor <pjt47@cam.ac.uk>, Julian Reschke <julian.reschke@gmx.de>, Lachlan Hunt <lachlan.hunt@lachy.id.au>, "public-html@w3.org" <public-html@w3.org>
Message-ID: <20100217143033661769.95d5ae75@xn--mlform-iua.no>
Maciej Stachowiak, Wed, 17 Feb 2010 05:26:40 -0800:
> 
> On Feb 17, 2010, at 5:17 AM, Leif Halvard Silli wrote:
> 
>> Philip Taylor, Wed, 17 Feb 2010 09:29:43 +0000:
>>> Julian Reschke wrote:
>>>> On 17.02.2010 10:08, Lachlan Hunt wrote:
>>>>> Leif Halvard Silli wrote:
>>>>>> Not in Safari 4. In the current version of Safari, this variant of the
>>>>>> strict Doctype triggers QuirksMode:
>>>>>> 
>>>>>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
>>>>>> [<!ATTLIST P myattr CDATA #implied>]>
>>>>> 
>>>>> This is a bogus DOCTYPE in HTML5 because there is no support for parsing
>>>>> the SGML syntax for the internal subset in the HTML serialisation. [...]
>>>> 
>>>> ...just trying to understand... a DOCTYPE that previously triggered
>>>> standards mode will now (as in FF trunk + HTML5 parser) get you to
>>>> Quirks mode?
>>> 
>>> Yes, but in pre-HTML5 browsers (IE, Firefox 3.6 without html5.enable,
>>> etc) doctypes will still only be parsed up to the *first* ">", so you
>>> will get the characters "]>" inserted as text into the body of the
>>> document, so today you can't use internal subsets in text/html anyway.
>> 
>> Firefox and IE do indeed show the "]>". Opera and Konqueror do not.
>> Safari 4 does show it, but since Konqueror does not, then I don't trust
>> that this is a "honest" display. As this test page shows:
>> http://www.målform.no/html4-or-html5/

> 
> What do you mean by "honest"? WebKit forked from KHTML years ago. One 
> of the earliest things rewritten was the doctype parsing code, where 
> we did our best to copy Gecko. It's not at all surprising that the 
> behavior is different.

If that is so, then it of course sounds likely that it is an old issue. 
However, if you have copied Firefox so well, then it has to be a new 
that it triggers QuirksMode. Because it does not in released Firefox.
-- 
leif halvard silli
Received on Wednesday, 17 February 2010 13:31:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:02 GMT