W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

Re: Mutation events replacement

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 30 Jun 2011 15:26:58 -0400
Message-ID: <4E0CCE02.6070608@mit.edu>
To: public-webapps@w3.org
On 6/30/11 2:56 PM, David Flanagan wrote:
> I'll add my own possibly stupid question... Can we go in the opposite
> direction and fire mutation events immediately without queuing, but
> forbid any DOM modifications from the event callbacks?

Forbid DOM modifications to all DOMs?  Or just one DOM?  Is 
window.close() forbidden?  Is spinning the event loop (e.g. sync XHR) 

This is actually a pretty hard problem to solve, and still wouldn't 
really solve the performance issues for DOM events....

Received on Thursday, 30 June 2011 19:27:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:20 UTC