W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: Mutation events replacement

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Wed, 20 Jul 2011 20:19:27 +0200
To: Boris Zbarsky <bzbarsky@MIT.EDU>
Cc: public-webapps@w3.org
Message-ID: <9v5e275bqk22gv3qj85kp8dtm816j6mqs2@hive.bjoern.hoehrmann.de>
* Boris Zbarsky 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 and additionally limit when the values
are available (further style changes made by the listener could in-
validate the information and you'd get an exception on access, for
instance). So the information being available as part of the API does
not necessarily imply performance problems.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Wednesday, 20 July 2011 18:19:41 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:46 GMT