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.
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>".
On Fri, Jun 4, 2010 at 00:16, TAMURA, Kent <tk...@chromium.org> wrote:
> An element is a "candidate for constraint validation" if
> 1. it is a validatable type,
> e.g. true if <input type=number>, false if <input type=reset>
> 2. has no "disabled" attribute,
> 3. has no "readonly" attribute,
> 4. inside of a <form> element,
> 5. has non-empty "name" attribute, and
> 6. not inside of a <datalist> element.
>
> I hope ValidityState and the pseudo classes ignores 2-6.
The pseudo-classes do not ignore 2, 3, and 6. (4 and 5 are now removed.)
I'd like to propose to add another condition:
7. it is visible (computed 'display' property of CSS isn't 'none' and no
'hidden' content attribute)
I couldn't find exceptional rules for validating invisible controls in the
current draft.
Chrome 5 was released with a part of interactive validation, and we
received a bug report about validation against invisible form controls.
--
TAMURA Kent
Software Engineer, Google
--
TAMURA Kent
Software Engineer, Google
