- From: <bugzilla@jessica.w3.org>
- Date: Wed, 10 Apr 2013 06:20:41 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21641
Dominic Cooney <dominicc@chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dominicc@chromium.org
--- Comment #3 from Dominic Cooney <dominicc@chromium.org> ---
I support this change. This simplifies the state machine which controls whether
I should start doing actions (animation, retrieving stuff, event listening,
etc.) and stop doing actions.
Olli: It seems unfortunate to for custom element authors to use
MutationObservers for this. All created custom elements will need to register
mutation observers over the entire document to see whether one of their
elements is inserted anywhere.
It seems much more efficient for implementations and simpler for authors if the
UA provides these callbacks. I *think* it is fine for the callbacks to be timed
to the microtask like a MutationObserver to avoid the pathologies of
MutationEvents.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 10 April 2013 06:20:42 UTC