- From: <bugzilla@jessica.w3.org>
- Date: Fri, 23 Sep 2011 23:37:50 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13401 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #14 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-09-23 23:37:49 UTC --- sicking: The idea is that you would point all the places that affect the checkbox at the same command, so that the buttons, keyboard shortcuts, etc, all end up driven by the same underlying checkbox logic, and the author doesn't have to worry about it. (This isn't yet in the spec, admittedly.) The behaviour you describe for the Window menu is a radio button menu item, not a checkbox. For checkboxes, I could maybe see an argument for letting authors check and uncheck things. For radio buttons, though, that's just a pain. Surely you agree that radio buttons should be automatic? I've fixed the definition of the activation behaviour (so it doesn't fire a second click event, d'oh). It is still unlike the <input> element in that the .checked value isn't changed until after the click event has fired (and not been canceled), though. 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: see above -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 23 September 2011 23:37:56 UTC