[e] (0) Try to clarify how UAs can abort at parse errors.

Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=21831 Affected topics: HTML Syntax and Parsing git-svn-id: http://svn.whatwg.org/webapps@7912 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Jun 5, 2013 · 4730462 · 4730462
1 parent df7bc16
commit 4730462
Show file tree

Hide file tree

Showing 3 changed files with 18 additions and 15 deletions.
diff --git a/complete.html b/complete.html
@@ -84248,6 +84248,7 @@ <h4 id=comments><span class=secno>12.1.6 </span>Comments</h4>
   <div class=impl>
 
   <h3 id=parsing><span class=secno>12.2 </span>Parsing HTML documents</h3>
+<!--CLEANUP-->
 
   <p><i>This section only applies to user agents, data mining tools,
   and conformance checkers.</i></p>
@@ -84287,9 +84288,10 @@ <h3 id=parsing><span class=secno>12.2 </span>Parsing HTML documents</h3>
   <p>This specification defines the parsing rules for HTML documents,
   whether they are syntactically correct or not. Certain points in the
   parsing algorithm are said to be <dfn id=parse-error title="parse error">parse
-  errors</dfn>. The error handling for parse errors is well-defined:
-  user agents must either act as described below when encountering
-  such problems, or must abort processing at the first error that they
+  errors</dfn>. The error handling for parse errors is well-defined
+  (that's the processing rules described throughout this specification), but 
+  user agents, while parsing an HTML document, may <a href=#abort-a-parser title="abort a
+  parser">abort the parser</a> at the first <a href=#parse-error>parse error</a> that they
   encounter for which they do not wish to apply the rules described
   in this specification.</p>
 
@@ -84298,8 +84300,7 @@ <h3 id=parsing><span class=secno>12.2 </span>Parsing HTML documents</h3>
   the document and must not report parse error conditions if none
   exist in the document. Conformance checkers may report more than one
   parse error condition if more than one parse error condition exists
-  in the document. Conformance checkers are not required to recover
-  from parse errors.</p>
+  in the document.</p>
 
   <p class=note>Parse errors are only errors with the
   <em>syntax</em> of HTML. In addition to checking for parse errors,

diff --git a/index b/index
@@ -84248,6 +84248,7 @@ dictionary <dfn id=storageeventinit>StorageEventInit</dfn> : <a href=#eventinit>
   <div class=impl>
 
   <h3 id=parsing><span class=secno>12.2 </span>Parsing HTML documents</h3>
+<!--CLEANUP-->
 
   <p><i>This section only applies to user agents, data mining tools,
   and conformance checkers.</i></p>
@@ -84287,9 +84288,10 @@ dictionary <dfn id=storageeventinit>StorageEventInit</dfn> : <a href=#eventinit>
   <p>This specification defines the parsing rules for HTML documents,
   whether they are syntactically correct or not. Certain points in the
   parsing algorithm are said to be <dfn id=parse-error title="parse error">parse
-  errors</dfn>. The error handling for parse errors is well-defined:
-  user agents must either act as described below when encountering
-  such problems, or must abort processing at the first error that they
+  errors</dfn>. The error handling for parse errors is well-defined
+  (that's the processing rules described throughout this specification), but 
+  user agents, while parsing an HTML document, may <a href=#abort-a-parser title="abort a
+  parser">abort the parser</a> at the first <a href=#parse-error>parse error</a> that they
   encounter for which they do not wish to apply the rules described
   in this specification.</p>
 
@@ -84298,8 +84300,7 @@ dictionary <dfn id=storageeventinit>StorageEventInit</dfn> : <a href=#eventinit>
   the document and must not report parse error conditions if none
   exist in the document. Conformance checkers may report more than one
   parse error condition if more than one parse error condition exists
-  in the document. Conformance checkers are not required to recover
-  from parse errors.</p>
+  in the document.</p>
 
   <p class=note>Parse errors are only errors with the
   <em>syntax</em> of HTML. In addition to checking for parse errors,

diff --git a/source b/source
@@ -94006,6 +94006,7 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
   <div class="impl">
 
   <h3 id="parsing">Parsing HTML documents</h3>
+<!--CLEANUP-->
 
   <p><i>This section only applies to user agents, data mining tools,
   and conformance checkers.</i></p>
@@ -94045,9 +94046,10 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
   <p>This specification defines the parsing rules for HTML documents,
   whether they are syntactically correct or not. Certain points in the
   parsing algorithm are said to be <dfn title="parse error">parse
-  errors</dfn>. The error handling for parse errors is well-defined:
-  user agents must either act as described below when encountering
-  such problems, or must abort processing at the first error that they
+  errors</dfn>. The error handling for parse errors is well-defined
+  (that's the processing rules described throughout this specification), but 
+  user agents, while parsing an HTML document, may <span title="abort a
+  parser">abort the parser</span> at the first <span>parse error</span> that they
   encounter for which they do not wish to apply the rules described
   in this specification.</p>
 
@@ -94056,8 +94058,7 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
   the document and must not report parse error conditions if none
   exist in the document. Conformance checkers may report more than one
   parse error condition if more than one parse error condition exists
-  in the document. Conformance checkers are not required to recover
-  from parse errors.</p>
+  in the document.</p>
 
   <p class="note">Parse errors are only errors with the
   <em>syntax</em> of HTML. In addition to checking for parse errors,