- From: <bugzilla@jessica.w3.org>
- Date: Mon, 27 Feb 2012 23:52:02 +0000
- To: public-html@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16142
Summary: Spec delivery semantics for MutationObservers
Product: HTML WG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: HTML5 spec (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: adamk@chromium.org
QAContact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
public-html@w3.org, annevk@opera.com
>From http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1622.html
"Delivery of MutationRecords happens asynchronously, at the end of
the current “microtask”. This is between Options 2 and 3 from this
discussion
http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/0780.html.
Instead of calling listeners at the end of outermost DOM operation or
at the end of a Task, listeners are called at the end of outermost
script invocation. If there are no script invocations, listeners are
called at the end of Task."
See http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#mutation-observers
for the current language. Specifically, "delivery" above means "invoking the
MutationCallback associated with a registered observer" passing it the current
"record queue" of that observer, and clearing the queue (just before
invocation).
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 28 February 2012 05:53:22 UTC