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

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

Rafael Weinstein <rafaelw@chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rafaelw@chromium.org

--- Comment #4 from Rafael Weinstein <rafaelw@chromium.org> ---
my $.02:

If you are processing every mutation as if it were a childlist, you're doing
something wrong and likely to get the wrong answer. 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.

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.

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