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 8670 - Parent for radiobuttons with same radiogroup
Summary: Parent for radiobuttons with same radiogroup
Status: RESOLVED WONTFIX
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://www.w3.org/TR/html5/interactiv...
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2010-01-07 10:49 UTC by Gez Lemon
Modified: 2010-10-04 13:57 UTC (History)
4 users (show)

See Also:


Attachments

Description Gez Lemon 2010-01-07 10:49:54 UTC
Radio buttons can be grouped using the @radiogroup attribute.  The algorithm described seems to require that radiobuttons with the same radiogroup have the same parent.  This is not required of <input type=radio> now, and it's pretty common for them not to have the same parent.  Why is this required?
Comment 1 Ian 'Hixie' Hickson 2010-02-05 20:51:18 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: I assume you are referring to the <command> element. If so, then the requirement is to ensure that context menus remain accessible, since having different context menus be involved in the same radio menuitem set would be an accessibility and usability nightmare.
Comment 2 Michael Cooper 2010-02-11 17:26:40 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.