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

Re: Mutation events replacement

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Sat, 02 Jul 2011 23:50:45 -0400
Message-ID: <4E0FE715.1060703@mit.edu>
To: public-webapps@w3.org
On 7/2/11 1:46 PM, John J. Barton wrote:
> 2) element transformation. The replacement fires "after" a mutation.
> Library or tools that want to transform the application dynamically want
> to get notification "before" the mutation. A common solution then is
> to bracket changes:
> "beforeChange" or "onModelChanging"
> "afterChange" or "onModelChanged"

This really only works if you trust the listeners.  The browser core 
can't trust scripted listeners using Web APIs.....

>  So, for example, I can't see how to implement
> JS pre-processing using only the after event. (This may not be
> possible with the current mutation events either, but it is something
> I want to to).

It's not clear that you need a web-facing API for your use case, though....

-Bori
Received on Sunday, 3 July 2011 03:51:25 GMT

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