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

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

Rafael Weinstein <rafaelw@chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adamk@chromium.org,
                   |                            |dglazkov@chromium.org

--- Comment #8 from Rafael Weinstein <rafaelw@chromium.org> ---
After talking with Adamk, I think I'm now convinced that there is a judgement
question about whether custom element callbacks should be sync by default or
async by default.

One can *basically* be structured in terms of the other. In particular, let's
imagine that all custom elements end up exposing new API and all those getters
wish to present synchronous abstractions, thus they all call *takeRecords*
before returning a value. This is effectively re-creating the behavior of
pseudo-sync events.

Alternatively, given the existing of MutationObservers, if the events are sync
by default, the callback can also choose to delay processing till the end of
the microtask via a mutation observer.

So the question is probably a judgement call about whether custom elements
*should* be generally presenting synchronous API boundaries or not.

Thanks, Adamk, for the thoughtful point.

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

Received on Thursday, 6 June 2013 17:17:04 UTC