W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2010

[Bug 10221] Always coalesce adjacent text nodes even in the case where the previous node was not the one last inserted by the parser.

From: <bugzilla@jessica.w3.org>
Date: Thu, 22 Jul 2010 08:24:49 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Obr5F-0008KD-69@jessica.w3.org>

Henri Sivonen <hsivonen@iki.fi> changed:

           What    |Removed                     |Added
                 CC|                            |hsivonen@iki.fi

--- Comment #1 from Henri Sivonen <hsivonen@iki.fi>  2010-07-22 08:24:48 ---
My current thinking is that the parser should coalesce. If that's a perf
problem when the node size gets very large, then I think implementors should
invoke the DoS avoidance limits trump card cause in the spec and not coalesce
too large nodes in any situation--be it foster-parenting, document.write() or
discretionary flushes for incremental layout of huge text nodes.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 22 July 2010 08:24:50 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:52 UTC