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

Re: Mutation events replacement

From: John J. Barton <johnjbarton@johnjbarton.com>
Date: Mon, 04 Jul 2011 20:36:26 -0700
Message-ID: <4E1286BA.9040500@johnjbarton.com>
To: public-webapps@w3.org
On 7/4/2011 6:34 PM, Boris Zbarsky wrote:
> On 7/4/11 12:09 PM, John J. Barton wrote:
>> In the current proposal, the DOM API is manipulated while the
>> onModelChange mutation listeners run.
>
> Citation please?  I see nothing like that in the proposal.
http://www.mail-archive.com/public-webapps@w3.org/msg14008.html

The only undesirable feature is that code that mutates the DOM from
inside a callback, say by calling setAttribute, can't rely on that by
the time that setAttribute returns,


>
>> In the present case, imagine that the mutation listeners have only one
>> function call available: onNextTurn().
>
> How do you ensure that given that the arguments include DOM nodes 
> which then transitively allow you to reach all of the DOM's 
> functionality?
By making all such calls fail.

jjb
>
> -Boris
>
Received on Tuesday, 5 July 2011 03:36:47 GMT

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