[Bug 21969] [Custom]: add attributeChangedCallback to the set of prototype callbacks

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21969

--- Comment #19 from Scott Miles <sjmiles@chromium.org> ---
re: "[talking to Scott] it's not obvious ... that more synchronous semantics
are actually necessary"

Yes, I agree that my stance was confusing. Unfortunately, I've been trying to
thread the needle by agreeing that fully asynchronous semantics are sane while
suggesting nobody will like it.

I'm more inclined now to take a harder line and just say that `readyCallback`
and `attributeCallbackChanged` must be synchronous (to JavaScript, not to any
internal process).

I'm way less concerned about `inserted|removedCallback`, which IMO can simply
be asynchronous.

Sorry for the confusion about MutationObservers; since I think of that API as
the vanguard for asynchrony, the notion that it would be the answer for
synchrony eluded my consciousness. :P

Thank you as always for your patience.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 11 June 2013 02:01:22 UTC