[whatwg] Form validation against invisible controls
Ola P. Kleiven
olak at opera.com
Mon Jun 14 02:55:20 PDT 2010
On Mon, 14 Jun 2010 07:41:40 +0200, Peter Kasting <pkasting at google.com>
> On Sun, Jun 13, 2010 at 10:16 PM, TAMURA, Kent <tkent at chromium.org>
>> There are some objections against omitting invisible controls from form
>> validation. However, it is a real issue with existing sites and users
>> submit such forms at all though they can submit it with non-HTML5
> How many existing sites? What sites are asking for form validation but
> not actually working with it? If this isn't a large number, I would
> to stay as-is and let the sites fix themselves.
The following sites have workarounds in Opera's browser.js to allow form
airgreenland.com (using required on hidden elements)
barnesandnoble.com (using required on visible elements that are supposed
to be empty on submit...)
bookryanair.com (using required=false - this usage has also been found in
ingdirect.com.au (using required on a visible field, but then emptying the
field with JS before submit)
usairways.com (using required on hidden elements)
Most of these have been using it for several years and have not responded
to change requests from our side.
We have also seen a couple of instances of wrong input types (number where
text expected etc.), but the usage of "required" is the biggest problem in
> My conclusion is it's better to disable interactive form validation for
>> existing sites as possible. e.g. disabling interactive form validation
>> documents without "<!DOCTYPE html>".
> I think this is a mistake.
Ola P. Kleiven, Core Compatibility, Opera Software
More information about the whatwg