On Tue, 30 Dec, 2014 at 5:12 PM, Garrett Smith <dhtmlkitc...@gmail.com> wrote:

 - alerts false

This result, in a way, seems to contradict the following:-

| The disabled attribute, when specified, causes all
| the form control descendants of the fieldset element,
| excluding those that are descendants of the fieldset
| element's first legend element child, if any, to be disabled.


This behaviour is useful from the user's perspective: If a user first disables then re-enables a fieldset, the disabled state of descendant controls should persist. E.g. if the fieldset contains a control that is not disabled, then on re-enabling the fieldset the control should one again be not disabled.

The behaviour of the disabled attribute you find above makes sense under those circumstances: It reflects the disabled state of the control were its ancestor fieldsets (if any) not disabled - it doesn't reflect if it would included in a submission or not.

Given the variety of conditions in both the spec and in browser implementations that would make a control eligible for success, maybe it would be useful it have an attribute like 'enabled' - but what's the use case?


⊨ Michael Gratton, Percept Wrangler.
⚙ <http://mjog.vee.net/>

Reply via email to