- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Wed, 20 Jul 2011 14:38:25 -0400
- To: Bjoern Hoehrmann <derhoermi@gmx.net>
- CC: public-webapps@w3.org
On 7/20/11 2:19 PM, Bjoern Hoehrmann wrote: >> It's pretty common to have situations where lots (10-20) of properties >> are set in inline style, especially in cases where the inline style is >> being changed via CSS2Properties from script (think animations and the >> like, where the objects being animated tend to have width, height, >> various margin/border/padding/background properties, top, left, etc all >> set). Those are precisely the cases that are most performance-sensitive >> and where the overhead of serializing the style attribute on every >> mutation is highest due to the large number of properties set. > > Depending on the design of the mutation notification system and what > level of complexity people find palatable, it would naturally also be > possible to serialize lazily The only way to do that is to make sure the pre-mutation data is kept somewhere. Doing that is _expensive_. We (Gecko) have been there, done that, and moved away from it. >So the information being available as part of the API does > not necessarily imply performance problems. It really does, sorry.... -Boris
Received on Wednesday, 20 July 2011 18:39:09 UTC