Re: [whatwg] Why do HTML*Collection's nameItem need to return 5 different objects?

2012-12-14 Thread Ian Hickson
On Thu, 6 Sep 2012, Simon Pieters wrote: > On Wed, 05 Sep 2012 22:47:07 +0200, Ian Hickson wrote: > > > > http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1736 > > > > Webkit returns undefined, whereas IE, Gecko, and Opera all return an > > HTMLCollection. (IE returns an HTMLCollec

Re: [whatwg] Why do HTML*Collection's nameItem need to return 5 different objects?

2012-09-06 Thread Ojan Vafai
On Wed, Sep 5, 2012 at 1:47 PM, Ian Hickson wrote: > For HTMLOptionsElement, the situation is more murky. > >http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1739 > > From what I can tell, IE doesn't do direct named access, you have to do it > via item() or namedItem(). The spec di

Re: [whatwg] Why do HTML*Collection's nameItem need to return 5 different objects?

2012-09-06 Thread Simon Pieters
On Wed, 05 Sep 2012 22:47:07 +0200, Ian Hickson wrote: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1736 Webkit returns undefined, whereas IE, Gecko, and Opera all return an HTMLCollection. (IE returns an HTMLCollection with a tags() method, Gecko and Opera do not. The spec r

Re: [whatwg] Why do HTML*Collection's nameItem need to return 5 different objects?

2012-09-05 Thread Ian Hickson
On Fri, 13 Jul 2012, Ryosuke Niwa wrote: > On Fri, Jul 13, 2012 at 3:17 PM, Ian Hickson wrote: > > On Fri, 13 Jul 2012, Ryosuke Niwa wrote: > > > > > > *HTMLCollection* returns the first element. > > > > This is for compat in the default case, I believe. > > > > > *HTMLAllCollection* returns the f

Re: [whatwg] Why do HTML*Collection's nameItem need to return 5 different objects?

2012-07-13 Thread Ryosuke Niwa
On Fri, Jul 13, 2012 at 3:17 PM, Ian Hickson wrote: > On Fri, 13 Jul 2012, Ryosuke Niwa wrote: > > > > According to > > > http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html#htmlpropertiescollection > > > > *HTMLCollection* returns the first element. > > This is

Re: [whatwg] Why do HTML*Collection's nameItem need to return 5 different objects?

2012-07-13 Thread Ian Hickson
On Fri, 13 Jul 2012, Ryosuke Niwa wrote: > > According to > http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html#htmlpropertiescollection > > *HTMLCollection* returns the first element. This is for compat in the default case, I believe. > *HTMLAllCollection* re

[whatwg] Why do HTML*Collection's nameItem need to return 5 different objects?

2012-07-13 Thread Ryosuke Niwa
According to http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html#htmlpropertiescollection *HTMLCollection* returns the first element. *HTMLAllCollection* returns the first element or another HTMLAllCollection if there are multiple elements *HTMLFormControlsCollec