diff --git a/index b/index index 19c184a1d48..c9e8c2cdb37 100644 --- a/index +++ b/index @@ -975,7 +975,8 @@
  • 10.1 Obsolete elements
    1. 10.1.1 The body element
      2. -
    2. 10.1.2 The applet element
    • +
  • 10.1.2 The applet element
    • +
  • 10.2 Conformance checkers
  • 11 Things that you can't do with this specification because they are better handled using other technologies that are further described herein @@ -47594,13 +47595,13 @@ interface MessageChannel {

    If the DOCTYPE token's name is not an ASCII case-insensitive match for the string "HTML", or if the token's public identifier is neither missing nor equal to the string - "XSLT-compat", or if the token's system identifier - is not missing, then there is a parse - error. Conformance checkers may, instead of reporting this - error, switch to a conformance checking mode for another language - (e.g. based on the DOCTYPE token a conformance checker could - recognize that the document is an HTML4-era document, and defer to - an HTML4 conformance checker.)

    + "XSLT-compat", or if the token's system identifier is + not missing, then there is a parse error (this is the + DOCTYPE parse error). Conformance checkers may, instead + of reporting this error, switch to a conformance checking mode for + another language (e.g. based on the DOCTYPE token a conformance + checker could recognize that the document is an HTML4-era + document, and defer to an HTML4 conformance checker.)

    Append a DocumentType node to the Document node, with the name @@ -53582,13 +53583,58 @@ xh|section xh|section xh|section xh|section xh|section xh|h1 { /* same styles as attribute must return an HTMLCollection rooted at the Document node, whose filter matches only applet elements.

    - +

    10.2 Conformance checkers

    + +

    To ease the transition from HTML4 Transitional documents to the + language defined in this specification, conformance + checkers are encouraged to categorise errors that represent usage of + old obsolete features that generally have no effect (as defined + below) into a separate part of their report, to allow authors to + distinguish between likely mistakes and mere vestigial markup.

    + +

    The following errors may be categorised as described above:

    + +

    11 Things that you can't do with this specification because they are better handled using other technologies that are further described herein

    diff --git a/source b/source index 18cb44fa906..d10c5076237 100644 --- a/source +++ b/source @@ -54292,13 +54292,13 @@ interface MessageChannel { ASCII case-insensitive match for the string "HTML", or if the token's public identifier is neither missing nor equal to the string - "XSLT-compat", or if the token's system identifier - is not missing, then there is a parse - error. Conformance checkers may, instead of reporting this - error, switch to a conformance checking mode for another language - (e.g. based on the DOCTYPE token a conformance checker could - recognize that the document is an HTML4-era document, and defer to - an HTML4 conformance checker.)

    + "XSLT-compat", or if the token's system identifier is + not missing, then there is a parse error (this is the + DOCTYPE parse error). Conformance checkers may, instead + of reporting this error, switch to a conformance checking mode for + another language (e.g. based on the DOCTYPE token a conformance + checker could recognize that the document is an HTML4-era + document, and defer to an HTML4 conformance checker.)

    Append a DocumentType node to the Document node, with the name @@ -58484,7 +58484,78 @@ xh|section xh|section xh|section xh|section xh|section xh|h1 { /* same styles as attribute must return an HTMLCollection rooted at the Document node, whose filter matches only applet elements.

    - + + + +

    Conformance checkers

    + +

    To ease the transition from HTML4 Transitional documents to the + language defined in this specification, conformance + checkers are encouraged to categorise errors that represent usage of + old obsolete features that generally have no effect (as defined + below) into a separate part of their report, to allow authors to + distinguish between likely mistakes and mere vestigial markup.

    + +

    The following errors may be categorised as described above:

    + +