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 the spec is states: "command elements are not rendered unless they form part of a menu." it also states "The Hidden State of the command is true (hidden) if the element has a hidden attribute, and false otherwise." http://dev.w3.org/html5/spec/commands.html#using-the-command-element-to-define-a-command So shouldn't command elements that are not part of a menu always have a hidden state? Also please clarify in the spec what the purpose of a command element that is not part of a menu and thus never rendered is
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: I don't want to hardcode the states for <command>s in random places because that would preclude later using the command="" attribute idea with <command>s in random places. For now the only use of <command> in random places is to define a keyboard shortcut. I've mentioned that in the spec.
Checked in as WHATWG revision r5582. Check-in comment: mention what <command> can be used for http://html5.org/tools/web-apps-tracker?from=5581&to=5582
Confirming the text made it into http://www.w3.org/TR/html5/interactive-elements.html#the-command
Bug triage sub-team does not think this needs to be a TF priority. Assigning to Steve to confirm changes and close.