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

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

--- Comment #13 from Rafael Weinstein <rafaelw@chromium.org> ---
(In reply to comment #12)
> (In reply to comment #11)
> > What Anne said. You're usually the consistency guy =-). You don't find this
> > to be inconsistent with existing APIs?
> > 
> No. This is consistent with existing APIs.
> You get empty Nodelist all the time from various functions 
> (I know, we're dealing attributes here), but not null.
> 
> 
> Also, it would be inconsistent to have empty nodelist in case type
> is childList, but null in other cases.

I don't have any further defense for my position. I suppose it's stylistic. My
$.02 is that null for the case of non-childlist is correct. I defer to Anne to
make the call. FWIW, This doesn't strike me as "make-or-break" either way.

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