[whatwg] successful form controls

Kristof Zelechovski giecrilj at stegny.2a.pl
Sat Sep 15 06:14:09 PDT 2007

1. Radio buttons are never checked so this sentence means that they are
never successful.
2. A control that is read-only does not accept input from the user; however,
it may have a meaningful value that is worth submitting because its value
can be calculated on the client side.  Although the server can probably
recalculate the value on its own so that the value of the control is only
informative, I would hesitate making such controls uniformly unsuccessful.
If it is important, the control can be disabled by the designer.


-----Original Message-----
From: whatwg-bounces at lists.whatwg.org
[mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Garrett Smith
Sent: Friday, September 14, 2007 2:40 AM
To: whatwg at whatwg.org
Subject: [whatwg] successful form controls

I found a few mistakes in the spec.

5.1. Successful form controls
The controls that are successful are those that are included in the
submission (in the form data set) when their form is submitted.

All form controls are successful except:

Controls with no associated form.
Controls that are inside repetition templates (those that are in their
forms' templateElements list).
Controls that are inside datalist elements.
Controls with no name, except if they are image controls.
Disabled controls.
Checkboxes that are not checked.
Radio buttons that are not checked.
Submit buttons (including image buttons) that did not initiate the
current submission process.
Buttons of type button, reset, add, remove, move-up, or move-down.
Output controls.
File upload controls with no value selected, or with only values that
point to non-existent files.
Controls do not have to have a value to be successful.

 * Readonly controls (just like how it works in HTML 4)
 * controls within a fieldset that is disabled
 * controls whose associated FORM (either FIELDSET or FORM element) is
either disabled or readonly.

The WF2 spec does include the attribute disabled for a fieldset, but
does not say that disabling a fieldset has *any* effect whatsoever.
This, to me, seems to be an oversight.

posted last month:

Programming is a collaborative art.

More information about the whatwg mailing list