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 13589 - Checkboxes and Radioboxes
Summary: Checkboxes and Radioboxes
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other All
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.w3.org/mid/CAP5EyKjSa-oRyU...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-03 05:54 UTC by HTML WG bugbot
Modified: 2011-08-13 01:37 UTC (History)
5 users (show)

See Also:


Attachments

Description HTML WG bugbot 2011-08-03 05:54:52 UTC
public-html-comments posting from: "Anas R." <anas.ram@gmail.com>
http://www.w3.org/mid/CAP5EyKjSa-oRyUp=+3_6UgwWKwCEjrGQX8VRX7bDGo9ZFFw=AQ@mail.gmail.com

Hi all,

I think that checkboxs could be represented like this:
<checkbox>
    <li> </li>

<li> </li>

</checkbox>

I belive that the checkbox itself is just an attribute to an object called
List Item.
Check box is not an object.
Radia box is same.
Take a look to this demo for a form:
http://richstyle.org/download/Form/form.xml

Please See the source and the comments in it.

Anas R.
http://www.richstyle.org/
Comment 1 Tab Atkins Jr. 2011-08-03 15:17:02 UTC
What problem would this solve?  It appears to just be an alternate syntax for <input type=checkbox>.
Comment 2 Michael[tm] Smith 2011-08-04 05:13:03 UTC
mass-move component to LC1
Comment 3 Ian 'Hixie' Hickson 2011-08-13 01:37:46 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. Could you elaborate? Wouldn't this break backwards compatibility?