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 8673 - Restriction on command element as part of a menu
Summary: Restriction on command element as part of a menu
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Jason Kiss
QA Contact: HTML a11y API spec bugbot
URL:
Whiteboard:
Keywords: a11y, a11ytf, a11y_display
Depends on:
Blocks:
 
Reported: 2010-01-07 11:03 UTC by Gez Lemon
Modified: 2014-12-07 21:31 UTC (History)
9 users (show)

See Also:


Attachments

Description Gez Lemon 2010-01-07 11:03:40 UTC
The spec states: "command elements are not rendered unless they form part of a menu."

Suggest this restriction is removed. The Hotmail inbox example shows a real need for a generic multi-selection mechanism like this, even without a menu.
Comment 1 Ian 'Hixie' Hickson 2010-02-05 20:53:53 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: Did Not Understand Request
Change Description: no spec change
Rationale: I don't understand. What would it mean for <command> to be used outside of a menu???
Comment 2 Michael Cooper 2010-02-11 17:18:24 UTC
The HTML Accessibility Task Force intends to track these issues, per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html.
Comment 3 Michael Cooper 2010-08-28 14:26:07 UTC
http://www.w3.org/2002/09/wbs/44061/20080513_bugs/results#xq5

Take up in the mapping sub-group to develop a spec edit proposal. Assign the bug to Cynthia Shelly to track that this is addressed.
Comment 4 Cynthia Shelly 2011-12-23 19:21:57 UTC
moved to aapi mapping spec
Comment 5 Sam Ruby 2012-01-09 21:39:53 UTC
Removing TrackerIssue keyword based on component change.
Comment 6 Silvia Pfeiffer 2013-01-07 04:53:05 UTC
Would appreciate feedback on a commit that I just adopted from the WHATWG, which removes the <command> element and replaces it with a <menuitem> element:
https://github.com/w3c/html/commit/c5bcf8f2e230bc2a35a86d5cd6b873821de6c0bb

Also see the discussion at http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-December/038472.html .

It likely means that the a11y API document needs changing.

There is also the question whether we should adopt it for HTML5 CR or just use this as supporting evidence to remove <command> from HTML5 CR. This latter question should probably be discussed on list.
Comment 7 Jason Kiss 2013-08-03 00:53:27 UTC
(In reply to comment #6)

> It likely means that the a11y API document needs changing.

FYI, the a11y API document has been updated. <command> has been removed and mappings for <menuitem> in its three states provided:

http://rawgithub.com/w3c/html-api-map/master/index.html#el-100a
Comment 8 Jason Kiss 2014-12-07 21:28:54 UTC
Closing. <command> removed from spec. <menuitem> added a while ago to HTML A11y API Mappings.