This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
I do not really understand why it has been added to the specifications. I do not see any use case for that. The only one I found was to check which options were selected to keep an history and move the most clicked ones at the top of the list. However, .selectedOption doesn't return the option that has been really selected but the first option with a matching value. Though, even that use case doesn't seem that useful... So, is there a serious use case? Otherwise, we should probably consider removing this attribute.
IIRC the idea was consistency with <select>. But if we don't need it, I'm happy to remove it.
Looks like only Opera tries to implement it, and it doesn't actually implement it: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1213 So I removed it. 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 Rationale: Concurred with reporter's comments.
Checked in as WHATWG revision r6701. Check-in comment: Drop input.selectedOption since it has no compelling use cases and we don't have interop on it either. http://html5.org/tools/web-apps-tracker?from=6700&to=6701