W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2012

[whatwg] Can we make checkboxes readonly?

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 4 May 2012 21:05:35 -0700
Message-ID: <CAAWBYDCaePtL9CO_CcyUDOLzLqkXakxBZsCV+hJ7GBRx6f7jKg@mail.gmail.com>
On Wed, May 2, 2012 at 3:57 PM, Ian Hickson <ian at hixie.ch> wrote:
> On Wed, 6 Apr 2011, Tab Atkins Jr. wrote:
>> An app may dynamically set inputs or groups of inputs to readonly based
>> on app state. ?When you submit, though, it's impossible to tell (without
>> hacks) whether a checkbox was checked-but-disabled or just unchecked.
>> Handling the form data is *much* easier if you just get all the data,
>> regardless of whether, as a UI convenience, your app temporarily set
>> some of the inputs to readonly.
>
> That's a use case for submitting disabled check boxes, not for read-only
> checkboxes, IMHO. (The same could be said for disabled text controls.)

That's more-or-less what @readonly does - the input becomes "disabled"
but still submits.

~TJ
Received on Friday, 4 May 2012 21:05:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:08 GMT