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

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

--- Comment #11 from Rafael Weinstein <rafaelw@chromium.org> ---
(In reply to comment #10)
> (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?

What Anne said. You're usually the consistency guy =-). You don't find this to
be inconsistent with existing APIs?

> 
> > 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.