[Bug 27569] Move getElementsBy* to ParentNode?

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

Arkadiusz Michalski (Spirit) <crimsteam@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |crimsteam@gmail.com

--- Comment #4 from Arkadiusz Michalski (Spirit) <crimsteam@gmail.com> ---
I proposed the same thing for the same reason some time ago to Anne (via email)
but don't get any answer why not:), but happy that getElementById() was added
and now we can use it in DocumentFragment. 

Summary I thought that is the reason: nobody want extend usage of old
collection like HTMLCollection. But this change will be nice simplification for
specs and using for newbie; still see a lot of questions why
Document|DocumentFragment.getElementsBy* not work (the same was for
getElementById()). Maybe now I can read reason why they can't be move to
ParentNode.

Of course moving to NonElementParentNode also looks good, maybe some days old
jQuery disappear completely. But hmm:

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23860#c4

BZ:
[jQuery 1.2.5 assumes that any node it found in the DOM that has a
"getElementById" property is a Document node.  See
https://bugzilla.mozilla.org/show_bug.cgi?id=933193#c17}

so moving getElementsBy* to ParentNode will breake jQuery to?

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

Received on Thursday, 11 December 2014 15:32:15 UTC