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

Re: Mutation events replacement

From: Dave Raggett <dsr@w3.org>
Date: Thu, 21 Jul 2011 10:08:02 +0100
Message-ID: <4E27EC72.9000808@w3.org>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: public-webapps@w3.org
On 20/07/11 18:23, 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.

Thanks for the explanation. Apps would need a way to disable 
notifications during such animation sequences, and would be able to find 
another means to serialize the animation (at a higher level). This 
raises the question is unregistering and re-regtistering a mutation 
notification handler cheap or do we need an alternative mechanism for 
temporarily suspending notifications?

  Dave Raggett<dsr@w3.org>  http://www.w3.org/People/Raggett
Received on Thursday, 21 July 2011 09:08:40 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:34 UTC