[Bug 19402] MutationObservers: When appending a record to the queue the last item needs to be replaced if it represents the same mutation and the new record has an oldValue

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

--- Comment #1 from Anne <annevk@annevk.nl> ---
My understanding thus far is that this affects 'queue an "attributes" record'
and 'queue a "characterData" record'. 'queue a "childList" record' is fine as
it does not use the oldValue member and therefore does not require this.

To determine equality I suggest we simply check type/target and when type is
"attributes" we also check attributeName and attributeNamespace, for the last
record in the record queue.

Am I missing something? Mutation observer algorithms still manage to confuse me
:/

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

Received on Wednesday, 10 October 2012 09:58:32 UTC