This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8737 - Allowing option with no value to be a command
Summary: Allowing option with no value to be a command
Status: VERIFIED INVALID
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://http://www.w3.org/TR/html5/int...
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2010-01-14 11:16 UTC by Gez Lemon
Modified: 2010-10-09 14:26 UTC (History)
5 users (show)

See Also:

Attachments

Description Gez Lemon 2010-01-14 11:16:13 UTC 
The specification states: "An option element with an ancestor select element and either no value attribute or a value attribute that is not the empty string defines a command."

Why is option with no value considered a command?
Comment 1 Michael Cooper 2010-02-11 17:26:46 UTC 
Per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html, the HTML A11Y TF does not plan to formally work on this issue at this time. This does not mean the TF has no interest in it, but does not have immediate plans to work on it. The TF may review the issue in the future.
Comment 2 Ian 'Hixie' Hickson 2010-02-17 22:14:26 UTC 
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: Rejected
Change Description: no spec change
Rationale: It has a value, just no value attribute.

I'm not sure I entirely understand the premise of this bug. Please feel free to reopen it if I misunderstood the request.