[Bug 23694] Should element.getElementById() consider the element itself when searching

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

Glenn Maynard <glenn@zewt.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |glenn@zewt.org

--- Comment #5 from Glenn Maynard <glenn@zewt.org> ---
We only "expect" it to because we've been bit by it and learned its weird
behavior.  That doesn't mean it's how we *want* it to behave.

This can't be changed now, of course, but I definitely recall being annoyed at
querySelector not matching the top element, and having to manually
matchSelector it separately.  I don't know if it's worth adding a parameter,
though (if so, it should be a dictionary parameter and not a bare boolean).

(If we add a function to search up the tree, eg. "find the nearest container
that matches a selector", it absolutely needs to check the initial node,
though.)

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

Received on Sunday, 3 November 2013 23:48:28 UTC