[Bug 21338] Gut check on when to clear transient registered mutation observers

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21338

--- Comment #3 from Olli Pettay <bugs@pettay.fi> ---
So, when takeRecords() was added I was thinking, and still do, that it
shouldn't
affect to MutationRecord creation. It is just a way to get the current
records which can be then handled before the end of microtask.

There shouldn't be problem with double MutationRecords. There is just
one per mutation per MutationObserver.

Also, if you do want to clear transient observers, just disconnect()/observer()
after takeRecords().

So, it is not clear to me why we'd want to change the spec (also given that
there has been two compatible implementations shipping quite some time).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 25 March 2013 17:25:06 UTC