A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members) or send an e-mail to admin@wiki.whatwg.org with your desired username and an explanation of the first edit you'd like to make. (Do not use this e-mail address for any other inquiries, as they will be ignored or politely declined.)

Forms

From WHATWG Wiki
Jump to: navigation, search

This page collects feedback on what does not work with HTML forms. Having wider adoption of standard form controls benefits usability/accessibility so it is important that they work nicely.

UI

Input Validation

The bubble error message tooltips displayed by contemporary implementations do not offer enough flexibility in layout and therefore HTML form validation is slow to reach wider adoption. Despite the many benefits of having native form input validation, many sites still rely on fallbacks and polyfills to author custom designs.

Currently, HTML input validation messages are displayed as bubble tootlips only:

Form-validation-required.png

Existing webkit pseudo-elements for styling are limited in scope and do not meet use cases:

-webkit-validation-bubble
-webkit-validation-bubble-arrow-clipper
-webkit-validation-bubble-arrow
-webkit-validation-bubble-message

Use Cases

Use Case 1 - Inline Message

Allow error messages to be inserted immediately after the input field.

Example:

Audible-inline-validation.png

Use Case 2 - All Messages Shown

Allow all messages to be displayed at once for each invalid input field.

Example:

Sign-up-form-inline-error-messages.gif

Use Case 3 - Grouped Messages

Allow the error messages to be grouped for all error messages shown.

Example:

Validator-js-javascript-form-validation.jpg