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

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

--- Comment #3 from Olli Pettay <Olli.Pettay@gmail.com> 2011-07-28 09:34:59 UTC ---
(In reply to comment #1)
> <input>'s handling of check state is somewhat obtuse, I'm not sure we want to
> match it exactly. But maybe it's worth it for consistency?

Exactly, for consistency. If the command.checked handling is like
input.checked handling, the same scripts can be used to handle those.
It would be rather weird to have another checkbox-like API, which looks like
input elements API, but works in this essential case in a very different way.

-- 
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 Thursday, 28 July 2011 09:35:05 UTC