Simple use case with existing car configurators: When a car feature / accessory is selected that requires another feat. / access., I don't want customers to uncheck that feature, but still need the submission of the required features.
Or the Mootools library builder: Depending modules need to be selected and submitted in order to generate the correct javascript file. Yes, you can re-add that logic server-side, but why would you want to add that kind of logic twice. My 2 cents Randy -----Original Message----- From: Lachlan Hunt <[email protected]> Sender: [email protected]: Thu, 07 Apr 2011 00:39:04 To: Tab Atkins Jr.<[email protected]> Cc: WHATWG List<[email protected]> Subject: Re: [whatwg] Can we make checkboxes readonly? On 2011-04-07 00:28, Tab Atkins Jr. wrote: > On Wed, Apr 6, 2011 at 3:12 PM, Lachlan Hunt<[email protected]> wrote: >> What's wrong with using disabled? >> >> <input type="checkbox" disabled> >> <input type="checkbox" disabled checked> > > Disabled elements don't participate in form submission. That's true, but if the controls are readonly, then the user can't change the value and so why does that matter? Could you clarify the use case for having a readonly checkbox value submitted? -- Lachlan Hunt - Opera Software http://lachy.id.au/ http://www.opera.com/
