This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html Multipage: http://www.whatwg.org/C#htmlallcollection-0 Complete: http://www.whatwg.org/c#htmlallcollection-0 Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: Clarify the section on HTMLAllCollection Posted from: 81.242.199.134 by ms2ger@gmail.com User agent: Mozilla/5.0 (X11; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0
Quoting bz: > http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html#htmlallcollection-0 says > "The HTMLAllCollection interface is used for generic collections of elements just like HTMLCollection" > which is not true > it also says > "The supported property names consist of the non-empty values of all the id attributes of all the elements represented by the collection" > "and the non-empty values of all the name attributes of all the "all"-named elements represented by the collection" > and the place where it's defined what's represented is at http://www.whatwg.org/specs/web-apps/current-work/multipage/obsolete.html#dom-document-all > It _might_ be clearer to just note in the former text that the collection represents all elements in the document > instead of people having to chase the definitions and find where the thing was created to figure that out > And stuff like > "Let collection be an HTMLCollection object rooted at the same node as the HTMLAllCollection object on which the method was invoked, whose filter matches only elements that already match the filter of the HTMLAllCollection object on which the method was invoked " > The "filter of the HTMLAllCollection object" is "accept all elements" > so that text could just say that the filter matches only elements that satisfy one of the two bullets > and be way clearer
Fixed; see diff in bug 25817.