July 25, 2012 - TC39 Meeting Notes

Rafael Weinstein rafaelw at chromium.org
Mon Jul 30 16:26:54 PDT 2012

On Mon, Jul 30, 2012 at 2:56 PM, Aymeric Vitte <vitteaymeric at gmail.com> wrote:
> Le 28/07/2012 01:55, Rick Waldron a écrit :
>> Explanation of specification history and roots in newer DOM mutation
>> mechanism.
>> AWB: Is this sufficient for implementing DOM mutation event mechanisms?
>> RWS: Yes, those could be built on top of Object.observe
> Probably I must be misreading the proposal (again), but if you take a js DOM
> project where almost all attributes are handled via getters/setters, how can
> we observe something ?

The point wouldn't be to observe DOM changes directly via
Object.observe() by user script. The DOM Mutation API is different in
several ways from Object.observe() (different API surface area,
different vocabulary of changes, etc...)

One approach would be have the DOM storage internally be graphs of
simple data. The implementation can observe changes and then compute a
transform of the data changes it receives into the necessary DOM
mutations, which it then broadcasts.

I don't have an opinion of whether it would be a good idea to take
this approach (my guess is that standard trade-offs of complexity &
memory vs speed would apply). Allen's question was whether it would be

> --
> jCore
> Email :  avitte at jcore.fr
> Web :    www.jcore.fr
> Webble : www.webble.it
> Extract Widget Mobile : www.extractwidget.com
> BlimpMe! : www.blimpme.com
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss

More information about the es-discuss mailing list