Conformance & Status

What parts of the HTML5 validation API are ready for prime time? (: finished, : work-in-progress)

feature	status	comment
willValidate
setCustomValidity(message)
validity.valueMissing		(access via hyperform.ValidityState)
validity.typeMismatch		(access via hyperform.ValidityState)
validity.patternMismatch		(access via hyperform.ValidityState)
validity.tooLong		(access via hyperform.ValidityState)
validity.tooShort		(access via hyperform.ValidityState)
validity.rangeUnderflow		(access via hyperform.ValidityState)
validity.rangeOverflow		(access via hyperform.ValidityState)
validity.stepMismatch		(access via hyperform.ValidityState)
validity.badInput		(access via hyperform.ValidityState)
validity.customError		(access via hyperform.ValidityState)
validity.valid		(access via hyperform.ValidityState)
checkValidity()
reportValidity()
validationMessage
valueAsDate
valueAsNumber
valueLow / valueHigh		not started, yet
stepUp(n) / stepDown(n)
accept attribute		for type=file inputs. It’s useful to implement a check because there are browsers without support, that implement the File API.
support for novalidate
support for properties like element.pattern

Todo list and plans for the high-level API:

• Trigger an event before validating individual elements.

• Allow functions to hook into the actual validations to accept or reject inputs.

• Translate validation messages. We have some partial translations ready: https://github.com/hyperform/hyperform-l10n

• Allow specifying settings to customize the behavior of Hyperform (e. g., specifying a renderer for error messages).

• Idea: Add a means of linking two <input>s together so they get validated synchronously:

  hyperform.link(element1, element2);
  element1.reportValidity();
  // element2.reportValidity gets triggered automatically
  

Do you have a wish or an idea? File an issue and let us discuss it!

Next: This is the last page of the documentation. Why not take a look at the examples?