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

[Bug 9052] All DOCTYPE variants that trigger standards mode pre-HTML5 should continue to trigger standards mode in HTML5

From: <bugzilla@wiggum.w3.org>
Date: Thu, 18 Feb 2010 09:37:09 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Ni2on-0005JO-6R@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9052





--- Comment #3 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>  2010-02-18 09:37:08 ---
Philip T. pointed out that HTML5 does require Standards Mode whenever the
doctype contains a URL/System Identifier - provided that the internal DTD
subset section (in my example: "[<!ATTLIST P myattr   CDATA #implied >]") comes
*after* the System Identifier.

http://www.w3.org/mid/4B7C03BA.4050903@cam.ac.uk

As the draft says: 

"Anything else
    Parse error. Switch to the bogus DOCTYPE state. (This does not set the
DOCTYPE token's force-quirks flag to on.)"
http://dev.w3.org/html5/spec/Overview.html#before-doctype-system-identifier-state 

And, sure enough, Opera 10.5 Beta behaves exactly that way, as can be verified
in my Take 2 of the test 

http://www. xn--mlform-iua.no/html4-or-html5/take2

So does this mean that this bug is solved? No. I agree with the view of Boris
Z: «going from treating a doctype as standards to treating a doctype as quirks
seems like a bad idea to me»

http://www.w3.org/mid/4B7C0A50.305@mit.edu

On what basis can HTML5 say that this or that DOCTYPE should trigger QuirksMode
if it now triggers StandardsMode? Can it be a goal to punish authors for using
even a non-standard doctype? Or even to reward them with a method for
triggering QuirksMode?

In my view, no. If we consider that QuirksMode has any benefit, then we should
even define a specific HTML5 doctype that would trigger QuirksMode, so that
authors could author a page according to HTML5 syntax rules and still get
QuirksMode. (After all, HTML5 defines standards mode as the default.)

Remedy: 

To fix this bug, the section about "Parsing HTML documents" must be refined so
that *only* those doctypes and doctype patterns that are _known_ to cause
QuirksMode, will cause QuirksMode. As an exampe, all the HTML4 doctypes that W3
has produced and which are known to not cause QuirksMode, must continue to not
cause quirks mode, even if they contain a internal DTD subset (or DOCTYPE
comments or any other "stuff" that currently doesn't cause QuirksMode.) 


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 18 February 2010 09:37:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:11 UTC