[Webkit-unassigned] [Bug 35043] Strict DTD should always trigger strict mode, also when there is an internal subset

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Feb 17 17:29:51 PST 2010


Leif Halvard Silli <xn--mlform-iua at xn--mlform-iua.no> changed:

           What    |Removed                     |Added
           Priority|P3                          |P2

--- Comment #3 from Leif Halvard Silli <xn--mlform-iua at xn--mlform-iua.no>  2010-02-17 17:29:51 PST ---

  I'll just make it clear that it is not only about "other browsers", but also
about HTML5. HTML5 requires Standards Mode when there is a system identifier in
the DOCTYPE. While Safari doesn't  make any difference - regardless.

PAGES AFFECTED versus the issue of Quirks/Standards mode: 

  That QuirksMode is triggerd when it shouldn't, should have high priority:
Suggest priority 2.

  There are indeed not that many affected pages, compared to the whole Web. And
the effect of QuirksMode isn't easy to spot always, either, I think. HOWEVER,
the very issue of Quirks/Standards triggering via the DOCTYPE is important. It
is the only function that doctyps have in the HTML5 world.

  I assume that the current behaviour in Safari/Webkit is a result of adapting
to HTML5 and thus that internal subsets did not trigger QuirksMode in Safari 3.
 Adapting to HTML5 should at least not lead to more doctypes than those HTML5
specify becoming Quirks triggers.


  According to Jukka Korpela internal DTD subests is a very useful approach -
see after the last quotation in this message:

  It is not very fruitful to assume that private DTDs and internal DTD subsets
can only be used to add useless, invalid stuff. 

  An internal DTD subset can e.g. also be used to add a HTML5 feature - such as
the time element - to a HTML4 document. I don't see how it would be meaningful
to label such an effort as  "fooling validity checkers into accepting invalid
content". The HTML5 spec says that user agents should behave the same,
regardless of possible doctypes/versioning. The exception being QuirksMode, for
which HTML5 keeps a list of QuirksMode triggers.

  Nevertheless, whether internal DTD subsets are useful is not within the scope
of HTML5, as HTML5 only defines what triggers QuirksMode and what triggers
StandardsMode.  But in the HTML4 world and in the XHTML worlds, internal
subsets are by definition useful if one wants to use DTD based validation.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list