W3C home > Mailing lists > Public > public-html-admin@w3.org > April 2014

[Bug 25232] New: De-emphasis DOCTYPE: shift focus from ”required preamble” to ”required rendering mode”

From: <bugzilla@jessica.w3.org>
Date: Wed, 02 Apr 2014 16:25:58 +0000
To: public-html-admin@w3.org
Message-ID: <bug-25232-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25232

            Bug ID: 25232
           Summary: De-emphasis DOCTYPE: shift focus from ”required
                    preamble” to ”required rendering mode”
           Product: HTML WG
           Version: unspecified
          Hardware: PC
               URL: http://www.w3.org/html/wg/drafts/html/master/syntax.ht
                    ml#the-doctype
                OS: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: xn--mlform-iua@xn--mlform-iua.no
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org

SITUATION: 

  Spec makes clear that the requirement to use a conforming DOCTYPE is a legacy
behavior issue. Thus, the underlying logic is that we should get rid of the
legacy necessity.

  Then the spec goes on describing the DOCTYPE as 
   1) ”a required preamble” which 
   2) ”ensures that the browser makes a best-effort attempt at following 
      the relevant specifications”.
  I.e. spec says DOCTYPE triggers no-quirks mode.

  The problem is that neither of above two statements are completely true. How
true they are, depends on context:

1) Above spec quotations are true only for HTML pages in Web browsers.

2) Inside @srcdoc, the spec itself says that the DOCTYPE is optional:
  
http://www.w3.org/html/wg/drafts/html/master/single-page.html#attr-iframe-srcdoc
   Thus, DOCTYPE is not required for @srcdoc documents.

3) For HTML mail, the effect of DOCTYPE falls in 3 categories,
   with well known implementations in each category:

   A) DOCTYPE ignored, falling back to no-quirks, is implemented by
      * Web mail apps (because app itself is in no-quirks) Examples: 
        # Microsoft Outlook.com
        # Google Gmail
      * Mozilla Gaia of Firefox OS (because it’s a offline Webmail app?)

   B) DOCTYPE ignored, falling back to quirks mode. Implemented by:
      * Mozilla Thunderbird 
        (https://bugzilla.mozilla.org/show_bug.cgi?id=335499)
      * Microsoft Email app for Windows 8.1

   C) DOCTYPE treated same as in Web browsers:
      * Microsoft Windows Live Mail 2012 (latest release: 2014)
      * Microsoft Windows Mail,
      * Microsoft Outlook Express,
      * Apple Mail for OSX
      * Apple mail for iOS

    (Though this be another bug, my general proposal for HTML mail is
     that A) (DOCTYPE ignored, falling back to no-quirks) should be 
     the rule for HTML email.)


PROPOSAL:

  Rework the spec towards saying that

  a) conforming documents are required to be authored so that
     they cause no-quirks rendering.
  b) user agents are required to  
     EITHER treat the DOCTYPE as OPTIONAL,
            in which case the UA MUST always use no-quirks mode.
            (This ought to be preferred behavior for 'new' specs.)
     OR, they must adhere to the mode selection rules defines
            by the HTML specification.
  c) Sub sections of the spec and "sub specifications" may 
     give more specific rules for certain usage contexts and/or
     media types. Examples: @srcdoc, HTML email and Web mail.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 2 April 2014 16:26:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:37:35 UTC