This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In browsers that expose global interface objects, the options collection object either is or inherits from HTMLCollection, thus allowing changes to HTMLCollection.prototype to affect it. In HTML5, it does not inherit, so it will not be affected by HTMLCollection.prototype changes. This seems like a needless change in behavior. I think it would be better for compatibility to make HTMLOptionCollection inherit from HTMLCollection, add the extra methods, and define the differences in operation behavior in prose. Note: the change I suggest would require making HTMLCollection.namedItem return "object" instead of "Element". See also bug 8035.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Partially Accepted Change Description: see diff given below Rationale: Done, except I just put namedItem() in both interfaces so HTMLOptionsCollection overrides the other one.
Checked in as WHATWG revision r4323. Check-in comment: Make collections inherit from HTMLCollection http://html5.org/tools/web-apps-tracker?from=4322&to=4323