[webkit-dev] Why so many text nodes in the DOM? (especially ones with just whitespace)
eric at webkit.org
Thu Jun 17 14:07:41 PDT 2010
A does not follow from B in that sentence, that current memory
fragmentation means we need to strip whitespace nodes.
It would also be possible to create a special shared "\n" text node,
and have some sort of Copy On Write behavior. Again, more complexity.
Not sure if the complexity would be worth the perf win.
On Thu, Jun 17, 2010 at 12:45 PM, Gustavo Sverzut Barbieri
<barbieri at profusion.mobi> wrote:
> David, it's bit more than annoying, it's fragmenting memory for no
> good. In the long run on systems will small memory it does make a
> difference :-/
> I'd like to see some option, maybe compile-time, to strip these
> useless whitespaces.
> On Thu, Jun 17, 2010 at 3:51 PM, David Hyatt <hyatt at apple.com> wrote:
>> Although it's annoying that these extra whitespace nodes are in the DOM, we do at least make sure not to create renderers for them most of the time.
>> On Jun 17, 2010, at 1:37 PM, Alexey Proskuryakov wrote:
>>> 17.06.2010, в 9:53, Andreas Delmelle написал(а):
>>>> If WebKit chooses, for example, to ignore character events from the parser in nodes where logically it doesn't make sense to have stray characters
>>> That would break e.g. Web sites where JS accesses DOM in ways such as node.firstChild.nextSibling, or node.childNodes. We've previously seen similar breakage happen after changing WebCore parsing code.
>>> - WBR, Alexey Proskuryakov
>>> webkit-dev mailing list
>>> webkit-dev at lists.webkit.org
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
> Gustavo Sverzut Barbieri
> http://profusion.mobi embedded systems
> MSN: barbieri at gmail.com
> Skype: gsbarbieri
> Mobile: +55 (19) 9225-2202
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
More information about the webkit-dev