Re: Mutation events replacement

On 7/20/11 4:10 PM, Bjoern Hoehrmann wrote:
> Simple example: you get a notification whenever a script could observe
> the .getAttribute value changes, and you get it before the change is
> applied.

Right, the synchronous "will mutate" notification.

Having that does simplify things.  As discussed on this list earlier, 
this can only be done if you trust your callees or can enforce that your 
callees don't mess things up during the notification.  In this case, the 
former is clearly false and the latter would basically involve changing 
the spec for every single API in the platform to behave slightly 
differently during the "will mutate" notification.  I agree that if this 
constraint somehow didn't exist the design space would be bigger for 
mutation events.  But it does exist, and it doesn't seem practical so 
far to remove it...


Received on Thursday, 21 July 2011 02:17:19 UTC