On Tue, Aug 21, 2012 at 1:58 PM, Tab Atkins Jr. <[email protected]>wrote:
> On Tue, Aug 21, 2012 at 1:42 PM, Ojan Vafai <[email protected]> wrote: > > On Tue, Aug 21, 2012 at 1:01 PM, Tab Atkins Jr. <[email protected]> > > wrote: > >> On Tue, Aug 21, 2012 at 12:37 PM, Ojan Vafai <[email protected]> wrote: > >> > Meh. I think this loses most of the "CSS is so much more convenient" > >> > benefits. It's mainly the fact that you don't have to worry about > >> > whether > >> > the nodes exist yet that makes CSS more convenient. > >> > >> Note that this benefit is preserved. Moving or inserting an element > >> in the DOM should apply CAS to it. > >> > >> The only thing we're really losing in the dynamic-ness is that other > >> types of mutations to the DOM don't change what CAS does, and some of > >> the dynamic selectors like :hover don't do anything. > > > > > > Ah, I missed the "plus a mutation observer that reruns the mutations on > any > > nodes added to the document" bit. Ok, so this timing is very specific > then. > > It would get applied at the microtask time, not at the time the DOM was > > modified. Would it get applied before or after mutation observers get > > called? Seems like you'd want it to execute first. Calling it after > mutation > > observers would require an extra delivery of mutations after the > attributes > > are applied, which seems silly. > > I presume there's an ordering of mutation observers, such that ones > defined earlier in document history get the notifications first, or > somesuch? Correct. > If so, CAS should indeed run before any author-defined > observers. On a somewhat unrelated note, could we somehow also incorporate jquery style live event handlers here? See previous www-dom discussion about this: . I suppose we'd still just want listen/unlisten(selector, handler) methods, but they'd get applied at the same time as cascaded attributes. Although, we might want to apply those on attribute changes as well.
