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 Chat (such as one of these permanent autoconfirmed members).
Forms: Difference between revisions
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
Currently, HTML input validation messages are displayed as bubble tootlips only: | Currently, HTML input validation messages are displayed as bubble tootlips only: | ||
[[File: | [[File: bubble-error.png]] | ||
Existing webkit pseudo-elements for styling are limited in scope and do not meet use case requirements: | Existing webkit pseudo-elements for styling are limited in scope and do not meet use case requirements: | ||
| Line 26: | Line 26: | ||
''Example'': | ''Example'': | ||
[[File: | [[File: inline-error.gif]] | ||
'''Requirement Use Case 2 - All Messages Shown''' | '''Requirement Use Case 2 - All Messages Shown''' | ||
| Line 34: | Line 34: | ||
''Example'': | ''Example'': | ||
[[File: | [[File: grouped-errors.gif]] | ||
'''Requirement Use Case 3 - Grouped Messages''' | '''Requirement Use Case 3 - Grouped Messages''' | ||
Revision as of 18:43, 18 May 2012
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:
Existing webkit pseudo-elements for styling are limited in scope and do not meet use case requirements:
- -webkit-validation-bubble
- -webkit-validation-bubble-arrow-clipper
- -webkit-validation-bubble-arrow
- -webkit-validation-bubble-message
Use Cases
Requirement Use Case 1 - Inline Message
Allow error messages to be inserted immediately after the input field.
Example:
Requirement Use Case 2 - All Messages Shown
Allow all messages to be displayed at once for each invalid input field.
Example:
Requirement Use Case 3 - Grouped Messages
Allow the error messages to be grouped for all error messages shown.
Example:
