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 20:43:04 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-20131-2532-AtnQs5nKqH@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20131

--- Comment #4 from Adam Klein <adamk@chromium.org> ---
WebKit shares records wherever possible to reduce the memory overhead of the
feature. Given that all attributes are readonly, this doesn't seem very
problematic (the worst that can happen is that the records become a
side-channel for expando properties; Events already have this behavior).

As Travis rightly points out, the existing queueing algorithm would need one
more loop to describe WebKit's behavior, since we at most create two records
for a given mutation (one with an oldValue and one without).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 28 November 2012 20:43:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 28 November 2012 20:43:06 GMT