W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > November 2012

[Bug 20131] [MutationObservers] Unclear whether unique record instances are required in 5.3.2 "Queuing a mutation record"

From: <bugzilla@jessica.w3.org>
Date: Wed, 28 Nov 2012 21:42:13 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-20131-2532-XmvT26SSg0@http.www.w3.org/Bugs/Public/>

--- Comment #9 from Olli Pettay <bugs@pettay.fi> ---
(In reply to comment #8)
> I don't think developers are likely to care much about the identity of
> records, but I do think they care about the memory footprint of the browsers
> they work in.

I do care about API consistency. That is what is exposed to the web.
Also, I believe memory usage won't be a problem in this case.
Mutation records should be short living objects and created
only within one microtask, so by far the most common case is to have just
few mutation records queued.
And, implementations are free share the record instances behind the
scenes. Just create different JS wrapper for each observer. That can be done in
quite cheap way, but is very much implementation detail.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 28 November 2012 21:42:15 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:04:28 UTC