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: document.all.item(5) not handled correctly 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
HTMLAllCollection only has an item() with a DOMString argument, so the one that takes an integer is shadowed.
Oh overload resolution doesn't cross inheritance boundaries?
That's correct. There are two separate item() functions here in JS terms: one takes any input and coerces to integer, the other takes any input and coerces to string. They live on different prototype objects, and one is shadowing the other.
Ok. Check the new prose, let me know if it's ok. I still inherit the 'getter', right? (The diff also contains fixes for editorial aspects of this section.)
Checked in as WHATWG revision r8645. Check-in comment: Various HTMLAllCollection fixes http://html5.org/tools/web-apps-tracker?from=8644&to=8645
I believe the indexed getter inherits, yes. It's a bit hard to tell from the WebIDL spec.