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: Thu, 29 Nov 2012 00:10:59 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-20131-2532-wsB3LsB6U6@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20131

--- Comment #18 from Olli Pettay <bugs@pettay.fi> ---
(In reply to comment #17)
> So your concern is that developers attempt to rely on records either always
> or never being shared?
Right.

And I'd prefer never sharing because that just makes the API more coherent.
Records delivered for observer Foo are never delivered for observer Bar.
That way script libraries can rely on that no one can alter their
records (if they use expandos for example). 

And so far I haven't seen cases where memory usage of records is problematic.
They are (usually) short living tiny objects.
Feel free to prove this wrong with a real world use case :)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 29 November 2012 00:11:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 29 November 2012 00:11:02 GMT