906333 - remove HTMLSelectElement.prototype.iterator

Status: RESOLVED INVALID

(Core :: DOM: Core & HTML, defect)

Description

[David Bruant]

Found that on Aurora 25. Not sure what that is.
From what I've seen it's not part of the standard
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html#htmlselectelement

It is also not listed in the latest webidl file (?)
https://hg.mozilla.org/mozilla-central/file/74fe1012de43/dom/webidl/HTMLSelectElement.webidl

Comment 1

[:Ms2ger (he/him; ⌚ UTC+1/+2)]

HTMLSelectElement has

  getter Element? item(unsigned long index);

which means that it gets an iterator. W3C bug is <https://www.w3.org/Bugs/Public/show_bug.cgi?id=17648>.

Comment 2

[Jean-Yves Perrier [:teoli]]

A question here: what triggers the creation of the iterator?
The method name + the getter clause?

(Would like to be able to know from the webidl which interface will have an iterator property.)

Comment 3

[:Ms2ger (he/him; ⌚ UTC+1/+2)]

"Having an indexed getter", i.e., a getter with an unsigned long argument.

Comment 4

[Jean-Yves Perrier [:teoli]]

Perfect thanx!

Comment 5

[David Bruant]

(In reply to :Ms2ger from comment #1)
> HTMLSelectElement has
> 
>   getter Element? item(unsigned long index);
> 
> which means that it gets an iterator. W3C bug is
> <https://www.w3.org/Bugs/Public/show_bug.cgi?id=17648>.
oh ok, I wasn't aware of that.
Also, I thought the agreement for iterator was a unique symbol... Alright I'll look up all of that.
Thanks for the quick response!

Comment 6

[David Bruant]

Ok, I looked into it and I believe a misunderstanding slipped through the cracks 
http://lists.w3.org/Archives/Public/public-script-coord/2013JulSep/0431.html
We'll see what people say.

Comment 7

[Peter Van der Beken [:peterv]]

This was added in bug 725907. I don't think we should remove this just from DOM objects if the JS engine still has support for this on the ES objects.