[Bug 13401] Make command.checked behavior consistent with input.checked

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13401

--- Comment #12 from Jonas Sicking <jonas@sicking.cc> 2011-08-23 06:49:03 UTC ---
(In reply to comment #11)
> (In reply to comment #10)
> > but I disagree with the
> > proposed remedy.
> I strongly disagree having another "checkbox API" which looks like
> the current <input type="checkbox">, but works in a very different way.

I don't think that a menu item with a checkbox looks anything like a <input
type=checkbox>. In fact, I think they are distinct enough that ideally we
shouldn't even use "type=checkbox" for menu items.

They neither look the same way visuall, nor act the same way when you click on
them. Additionally the actual check marks generally look differently.

If I look in my firefox menu right now (On Mac OSX), I see only a single menu
item with a check mark next to it. It's in the "Window" menu and signifies
which of all my firefox windows I currently have focused. If I click it it
doesn't uncheck the check mark. If I click another item in the menu it also
doesn't behave like a checkbox since it unchecks the item currently checked. In
other words, it acts much more like a radio box than a checkbox. Except that
it's rendered with a check mark rather than the bullet point which usually
signifies radios.

> > It's going to be very common to have several ways of activating commands,
> > for example through menu items, toolbar buttons and keyboard shortcuts. All
> > three will likely want to feed into the same status-updating function in
> > the JS code.
> Right. That is why we should add support for <menuitem command="somecommand">
> which
> will synchronize the state.

And that will make the check mark next to a menu item act even less like a
<input type=checkbox>

> > Additionally, if the code that handles the menuitem click sometimes fails
> > and throws an exception, for example due to exceptional circumstances like
> > network errors, out of database space or simply bugs,
> Those all are bugs which should be handled in the web app.

Indeed. But we should make the platform easy to develop for when we can.

-- 
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 Tuesday, 23 August 2011 06:49:05 UTC