[Bug 27320] Need some clarification around MutationObserver stuff.

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

--- Comment #2 from Arkadiusz Michalski (Spirit) <crimsteam@gmail.com> ---
Ok, callback case its clear.

Ehh... around "copy" I waste some time:), didn't realize that "copy list" just
copy list (where content of list is still original). But still don't understand
why list must be copy. In this alghoritm we don't modificate list but touch
only its content (MutationObserver objects), so contents of list and copy of
list looks/are the same.

To thank you for your explanation, this can be correct in "queue a mutation
record":

4.7 If observer has a paired string, set record's oldValue to observer's paired
string. << for /oldValue/ you can use reference (as we have in previous steps)

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

Received on Thursday, 13 November 2014 23:54:28 UTC