On Thu, Jun 17, 2010 at 6:24 PM, Matt 'Murph' Finnicum <mattf...@gmail.com> wrote: > On Thu, Jun 17, 2010 at 4:19 PM, David Hyatt <hy...@apple.com> wrote: >> >> On Jun 17, 2010, at 2:45 PM, Gustavo Sverzut Barbieri 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. >> > >> >> As Alexey points out, this is a compatibility issue though. People write >> code assuming the whitespace nodes are there. If you remove them, you'll >> see Web site breakage. >> >> dave >> (hy...@apple.com) >> > > Do people write code assuming the content of the whitespace nodes? That > seems very unlikely to me. If not, we could collapse them and be much more > efficient about things (such as a simple flag in their parent node that > represents their existence)
Same experience on my side, most JS libs that handle whitespace, do it just to ignore the nodes... running through strip and then checking for emptiness. -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
