- From: Bradley Meck <bradley.meck@gmail.com>
- Date: Mon, 12 May 2014 10:17:36 -0500
- To: "www-dom@w3.org" <www-dom@w3.org>
- Message-ID: <CANnEKUYHxUtUtJgx5LBxpt44wRxykY_sUu4TeX+G1nSyFzr_vg@mail.gmail.com>
See http://lists.w3.org/Archives/Public/www-dom/2013JulSep/thread.html#msg94, several threads spawned about MutationObservers. In the end people decided it was a wontfix https://www.w3.org/Bugs/Public/show_bug.cgi?id=23226 and all our hopes lie in custom notifications + Object.observe On Fri, May 9, 2014 at 3:44 PM, M. Klehr <mklehr@gmx.net> wrote: > Hello, > > I'd like to comment on the current spec for MutationObservers. > > Some that I have always found confusing is the differentiation between > properties and attributes of DOM Elements. As I am immersed in writing > scripts for the DOM, I usually interact with the DOM via the Node's > properties. Mostly, attributes and properties overlap, however there are > properties that don't mirror their corresponding attributes. > > For example, the `checked` property initially has the same value as its > attribute. However, when such an element is checked, the property value > changes whereas the attribute value does not. > As properties are part of the DOM, it would help very much if such > property changes were possible to be observed via MutationObservers. > > Kind regards, > Marcel Klehr >
Received on Monday, 12 May 2014 15:18:23 UTC