This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Out of Firefox nightly, Opera 10.62, Safari 5.0.2, Chrome 7.0.544 and IE9b, only Chrome implements the name getter. Is it needed? Can we remove it? It is redundant with the name getter on HTMLOptionsCollection. There are also many more names on HTMLSelectElement that would shadow the named properties compared to HTMLOptionsCollection.
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: Accepted Change Description: see diff given below (note: I also removed the 'caller' annotation) Rationale: Concurred with reporter's comments.
Checked in as WHATWG revision r5613. Check-in comment: Try to remove legacy crazy. If this breaks any pages please let me know. http://html5.org/tools/web-apps-tracker?from=5612&to=5613
mass-move component to LC1