NOTE: The current preferred location for bug reports is the GitHub issue tracker.
Bug 306 - Define when to coalesce text nodes in a less DOM-prone way. (credit: pt)
Define when to coalesce text nodes in a less DOM-prone way. (credit: pt)
Status: NEW
Product: Validator.nu
Classification: Unclassified
Component: HTML parser
HEAD
All All
: P2 normal
Assigned To: Nobody
http://svn.whatwg.org/webapps/source?...
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-09-25 11:51 CEST by Henri Sivonen
Modified: 2009-11-23 17:17 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 Henri Sivonen 2008-09-25 11:51:06 CEST
Index: source
===================================================================
--- source	(revision 2123)
+++ source	(revision 2124)
@@ -46244,10 +46244,11 @@
   <p>When the steps below require the UA to <dfn>insert a
   character</dfn> into a node, if that node has a child immediately
   before where the character is to be inserted, and that child is a
-  <code>Text</code> node, then the character must be appended to that
-  <code>Text</code> node; otherwise, a new <code>Text</code> node
-  whose data is just that character must be inserted in the
-  appropriate place.</p>
+  <code>Text</code> node, and that <code>Text</code> node was the last
+  node that the parser inserted into the document, then the character
+  must be appended to that <code>Text</code> node; otherwise, a new
+  <code>Text</code> node whose data is just that character must be
+  inserted in the appropriate place.</p>
 
   <p id="mutation-during-parsing">DOM mutation events must not fire
   for changes caused by the UA parsing the document. (Conceptually,