[whatwg] <output> should not be barred from constraint validation
Tab Atkins Jr.
jackalmage at gmail.com
Tue Jul 20 09:00:27 PDT 2010
On Tue, Jul 20, 2010 at 6:37 AM, Mounir Lamouri
<mounir.lamouri at gmail.com> wrote:
> At the moment, three form elements are barred from constraint
> validation: object, fieldset and output. I can understand why object and
> fieldset are barred from constraint validation but I think output could
> use the constraint validation.
> Indeed, it could be nice to be able to use setCustomValidity() on
> <output>. IMHO, it is part of the use case of <output>: this element
> should represent the result of a calculation and we may want to do a
> validation check on this result.
> For example, we could imagine a web application to choose courses in an
> university and you have to select between 12 and 18 credits. <output> is
> the best way to represent the total credits used and it would be easy to
> make it invalid when the sum is not correct.
I think that's actually pretty interesting. I might be able to get behind this.
More information about the whatwg