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: http://www.whatwg.org/C#htmloptionscollection-0 Complete: http://www.whatwg.org/c#htmloptionscollection-0 Comment: Need to mention the IDL concepts "indexed property setter and such are used. Posted from: 82.161.179.17 by annevk@annevk.nl User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.5 Safari/537.22
See also bug 20535.
I have no idea what's being requested here.
HTMLOptionsCollection uses various IDL concepts that are not referenced.
Why does anything need referencing? I still don't understand. What concept is not referenced that needs to be referenced? Did WebIDL change at some point?
The terms "set the value of an existing indexed property" and "determine the value of an indexed property" are not used. However, maybe IDL should not require specific names here but just an algorithm that goes with the IDL block.
I don't understand. Isn't this behaviour just inherited from HTMLCollection? Can you be more explicit about what you want to have changed? I really don't understand what you want changed here. As far as I can tell, the only thing this interface introduces is "set the value of a new indexed property", which I reference directly, and the named property getter, etc, use named operations.
Ms2ger points out that my creator is also a setter, so I've added "set the value of an existing indexed property". Is that sufficient?
Checked in as WHATWG revision r8212. Check-in comment: WebIDL doesn't default 'setter' to 'creator' (HTMLOptionsCollection) http://html5.org/tools/web-apps-tracker?from=8211&to=8212