[Bug 19463] MutationRecord added/removedNodes could return empty array, not null

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

--- Comment #10 from Olli Pettay <bugs@pettay.fi> ---
(In reply to comment #4)
>  It should be an
> invariant that a childlist mutation record has at least one node in either
> of added/removed nodes and code which tolerates both being empty is probably
> wrong.
Why such invariant?

> I think that having an empty array for added/removed in the case of
> non-childlist changes suggests something misleading about how the API works.
I see addedNodes and removedNodes as part of the MutationRecord.
You should always know whether something was added by checking
record.addedNodes.length.

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