NOTE: The current preferred location for bug reports is the GitHub issue tracker.
Bug 110 - DOCTYPE parsing: move the setting of the correctness flag to the places that call the bogus doctype state, so that we can later enter that state without triggering the correctness flag change. This change does not change the black box behaviour of the ...
DOCTYPE parsing: move the setting of the correctness flag to the places that ...
Status: RESOLVED FIXED
Product: Validator.nu
Classification: Unclassified
Component: HTML parser
HEAD
All All
: P2 normal
Assigned To: Henri Sivonen
http://svn.whatwg.org/webapps/source?...
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-03-03 13:13 CET by Nobody
Modified: 2008-03-13 16:22 CET (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nobody 2008-03-03 13:13:33 CET
Index: source
===================================================================
--- source	(revision 1304)
+++ source	(revision 1305)
@@ -37197,7 +37197,8 @@
       for the word "SYSTEM", then consume those characters and switch
       to the <span>before DOCTYPE system identifier state</span>.</p>
 
-      <p>Otherwise, this is the <span>parse error</span>. Switch to
+      <p>Otherwise, this is the <span>parse error</span>. Set the
+      DOCTYPE token's correctness flag to <i>incorrect</i>. Switch to
       the <span>bogus DOCTYPE state</span>.</p>
 
      </dd>
@@ -37243,8 +37244,9 @@
      EOF character in the <span>data state</span>.</dd>
 
      <dt>Anything else</dt>
-     <dd><span>Parse error</span>. Switch to the <span>bogus DOCTYPE
-     state</span>.</dd>
+     <dd><span>Parse error</span>.  Set the DOCTYPE token's
+     correctness flag to <i>incorrect</i>. Switch to the <span>bogus
+     DOCTYPE state</span>.</dd>
 
     </dl>
 
@@ -37346,7 +37348,8 @@
      EOF character in the <span>data state</span>.</dd>
 
      <dt>Anything else</dt>
-     <dd><span>Parse error</span>. Switch to the <span>bogus DOCTYPE
+     <dd><span>Parse error</span>. Set the DOCTYPE token's correctness
+     flag to <i>incorrect</i>. Switch to the <span>bogus DOCTYPE
      state</span>.</dd>
 
     </dl>
@@ -37390,7 +37393,8 @@
      EOF character in the <span>data state</span>.</dd>
 
      <dt>Anything else</dt>
-     <dd><span>Parse error</span>. Switch to the <span>bogus DOCTYPE
+     <dd><span>Parse error</span>. Set the DOCTYPE token's correctness
+     flag to <i>incorrect</i>. Switch to the <span>bogus DOCTYPE
      state</span>.</dd>
 
     </dl>
@@ -37483,7 +37487,8 @@
      EOF character in the <span>data state</span>.</dd>
 
      <dt>Anything else</dt>
-     <dd><span>Parse error</span>. Switch to the <span>bogus DOCTYPE
+     <dd><span>Parse error</span>. Set the DOCTYPE token's correctness
+     flag to <i>incorrect</i>. Switch to the <span>bogus DOCTYPE
      state</span>.</dd>
 
     </dl>
@@ -37499,14 +37504,12 @@
     <dl class="switch">
 
      <dt>U+003E GREATER-THAN SIGN (&gt;)</dt>
-     <dd>Set the DOCTYPE token's correctness flag to
-     <i>incorrect</i>. Emit that DOCTYPE token. Switch to the
-     <span>data state</span>.</dd>
+     <dd>Emit the DOCTYPE token. Switch to the <span>data
+     state</span>.</dd>
 
      <dt>EOF</dt>
-     <dd><span>Parse error</span>. Set the DOCTYPE token's correctness
-     flag to <i>incorrect</i>. Emit that DOCTYPE token.  Reconsume the
-     EOF character in the <span>data state</span>.</dd>
+     <dd><span>Parse error</span>. Emit the DOCTYPE token.  Reconsume
+     the EOF character in the <span>data state</span>.</dd>
 
      <dt>Anything else</dt>
      <dd>Stay in the <span>bogus DOCTYPE state</span>.</dd>
Comment 1 Nobody 2009-08-21 10:20:11 CEST
The original summary for this bug was longer than 255 characters, and so it was truncated when Bugzilla was upgraded. The original summary was:

DOCTYPE parsing: move the setting of the correctness flag to the places that call the bogus doctype state, so that we can later enter that state without triggering the correctness flag change. This change does not change the black box behaviour of the spec, but it can affect existing implementations that are tracking the spec.