NOTE: The current preferred location for bug reports is the GitHub issue tracker.
Bug 142 - The 'in table' fragment case still returned excessive parse errors. Also, fix a bit of the text in contentEditable to be clearer.
The 'in table' fragment case still returned excessive parse errors. Also, fix...
Classification: Unclassified
Component: HTML parser
All All
: P2 normal
Assigned To: Henri Sivonen
Depends on:
  Show dependency treegraph
Reported: 2008-03-10 15:53 CET by Nobody
Modified: 2008-03-11 20:12 CET (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Nobody 2008-03-10 15:53:09 CET
Index: source
--- source	(revision 1362)
+++ source	(revision 1363)
@@ -31013,8 +31013,8 @@
   false state, or all its ancestors have their <code
   title="attr-contenteditable">contenteditable</code> attribute set to
   the inherit state and the <code>Document</code> itself has <code
-  title="dom-document-designMode">designMode</code> disabled, and the
-  element is thus not editable.</p>
+  title="dom-document-designMode">designMode</code> disabled; either
+  way, the element is not editable.</p>
   <p>The <dfn
   title="dom-contentEditable"><code>contentEditable</code></dfn> DOM
@@ -40537,7 +40537,16 @@
    <dt>An end-of-file token</dt>
-    <p><span>Parse error</span>. <span>Stop parsing</span>.</p>
+    <p>If the <span>current node</span> is not the root
+    <code>html</code> element, then this is a <span>parse
+    error.</span>.</p>
+    <p class="note">It can only be the <span>current node</span> in
+    the <span>fragment case</span>.</p>
+    <p><span>Stop parsing.</span></p>
    <dt>Anything else</dt>
Comment 1 Henri Sivonen 2008-03-11 20:12:44 CET
Already taken care of.