Reorganize errors table in lexical order (#20)

HTMLParseErrorWG · Sep 11, 2017 · 813ea0b · 813ea0b
1 parent 87bc422
commit 813ea0b
Showing 1 changed file with 27 additions and 27 deletions.
diff --git a/source b/source
@@ -99918,18 +99918,18 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
      references as-is except C1 control references that are replaced according to the <span>numeric
      character reference end state</span>.</p>
 
-    <tr>
-     <td><dfn data-x="parse-error-end-tag-with-attributes">end-tag-with-attributes</dfn>
-     <td><p>This error occurs if the parser encounters an <span data-x="syntax-end-tag">end
-     tag</span> with <span data-x="syntax-attributes">attributes</span>. Attributes in end tags are
-     completely ignored and do not make their way into the DOM.</p>
-
     <tr>
      <td><dfn data-x="parse-error-duplicate-attribute">duplicate-attribute</dfn>
      <td><p>This error occurs if the parser encounters an <span
      data-x="syntax-attributes">attribute</span> in a tag that already has an attribute with the
      same name. The parser ignores all such duplicate occurrences of the attribute.
 
+    <tr>
+     <td><dfn data-x="parse-error-end-tag-with-attributes">end-tag-with-attributes</dfn>
+     <td><p>This error occurs if the parser encounters an <span data-x="syntax-end-tag">end
+     tag</span> with <span data-x="syntax-attributes">attributes</span>. Attributes in end tags are
+     completely ignored and do not make their way into the DOM.</p>
+
     <tr>
      <td><dfn data-x="parse-error-end-tag-with-trailing-solidus">end-tag-with-trailing-solidus</dfn>
      <td><p>This error occurs if the parser encounters an <span data-x="syntax-end-tag">end
@@ -100043,6 +100043,15 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
      <span data-x="syntax-attributes">attribute</span> value is expected (e.g., <code
      data-x="">&lt;div id=></code>). The parser treats the attribute as having an empty value.</p>
 
+    <tr>
+      <td><dfn data-x="parse-error-missing-doctype">missing-doctype</dfn>
+      <td>
+        <p>This error occurs if the parser encounters any content other than <span
+        data-x="syntax-comments">comments</span> or <span>ASCII whitespace</span> before <span
+        data-x="syntax-doctype">DOCTYPE</span> at the beginning of the document, i.e. DOCTYPE is not
+        a document preamble. In this case the parser sets the <code>Document</code> to <span>quirks
+        mode</span>.</p>
+
     <tr>
      <td><dfn data-x="parse-error-missing-doctype-name">missing-doctype-name</dfn>
      <td><p>This error occurs if the parser encounters a <span
@@ -100145,18 +100154,6 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
      --></code>). Such a comment will be closed by the first occuring "<code data-x="">--></code>"
      <span>code point</span> sequence and everything that follows will be treated as markup.</p>
 
-    <tr>
-     <td><dfn data-x="parse-error-noncharacter-character-reference">noncharacter-character-reference</dfn>
-     <td><p>This error occurs if the parser encounters a numeric <span
-     data-x="syntax-charref">character reference</span> that references a <span>noncharacter</span>.
-     The parser resolves such character references as-is.</p>
-
-    <tr>
-     <td><dfn data-x="parse-error-noncharacter-in-input-stream">noncharacter-in-input-stream</dfn>
-     <td><p>This error occurs if the <span>input stream</span> contains a <span>noncharacter</span>.
-     Such <span data-x="code point">code points</span> are parsed as-is and usually, where parsing
-     rules don't apply any additional restrictions, make their way into the DOM.</p>
-
     <tr>
      <td><dfn data-x="parse-error-non-conforming-doctype">non-conforming-doctype</dfn>
      <td><p>This error occurs if the parser encounters the <span
@@ -100189,6 +100186,18 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
       content to specify self-closing tags. (Self-closing tags don't exist in HTML.) It is also
       allowed for void elements, but doesn't have any effect in this case.</p>
 
+    <tr>
+     <td><dfn data-x="parse-error-noncharacter-character-reference">noncharacter-character-reference</dfn>
+     <td><p>This error occurs if the parser encounters a numeric <span
+     data-x="syntax-charref">character reference</span> that references a <span>noncharacter</span>.
+     The parser resolves such character references as-is.</p>
+
+    <tr>
+     <td><dfn data-x="parse-error-noncharacter-in-input-stream">noncharacter-in-input-stream</dfn>
+     <td><p>This error occurs if the <span>input stream</span> contains a <span>noncharacter</span>.
+     Such <span data-x="code point">code points</span> are parsed as-is and usually, where parsing
+     rules don't apply any additional restrictions, make their way into the DOM.</p>
+
     <tr>
      <td><dfn data-x="parse-error-null-character-reference">null-character-reference</dfn>
      <td><p>This error occurs if the parser encounters a numeric <span
@@ -100271,15 +100280,6 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
        data-x="">foo</code>" attribute to "<code data-x="">b'ar'</code>".</p>
      </div>
 
-    <tr>
-      <td><dfn data-x="parse-error-missing-doctype">missing-doctype</dfn>
-      <td>
-        <p>This error occurs if the parser encounters any content other than <span
-        data-x="syntax-comments">comments</span> or <span>ASCII whitespace</span> before <span
-        data-x="syntax-doctype">DOCTYPE</span> at the beginning of the document, i.e. DOCTYPE is not
-        a document preamble. In this case the parser sets the <code>Document</code> to <span>quirks
-        mode</span>.</p>
-
     <tr>
      <td><dfn data-x="parse-error-unexpected-equals-sign-before-attribute-name">unexpected-equals-sign-before-attribute-name</dfn>
      <td>