W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2010

[whatwg] Form validation against invisible controls

From: Ola P. Kleiven <olak@opera.com>
Date: Mon, 14 Jun 2010 11:55:20 +0200
Message-ID: <op.veaa6igfnw228i@id-c0814.oslo.osa>
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>  
> wrote:
>> There are some objections against omitting invisible controls from form
>> validation. However, it is a real issue with existing sites and users  
>> can't
>> submit such forms at all though they can submit it with non-HTML5  
>> browsers.
> How many existing sites?  What sites are asking for form validation but  
> then
> not actually working with it?  If this isn't a large number, I would  
> prefer
> 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  
JS libraries)
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 experience.

> My conclusion is it's better to disable interactive form validation for
>> existing sites as possible. e.g. disabling interactive form validation  
>> for
>> documents without "<!DOCTYPE html>".
> I think this is a mistake.
> PK

Ola P. Kleiven, Core Compatibility, Opera Software
Received on Monday, 14 June 2010 02:55:20 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:24 UTC