W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

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

From: <bugzilla@jessica.w3.org>
Date: Fri, 19 Aug 2011 12:54:22 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QuOac-00083p-W0@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13401

--- Comment #11 from Olli Pettay <Olli.Pettay@gmail.com> 2011-08-19 12:54:21 UTC ---
(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.

> 
> 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.


> 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.

-- 
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, 19 August 2011 12:54:24 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:17 UTC