W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2010

[whatwg] <output> should not be barred from constraint validation

From: Mounir Lamouri <mounir.lamouri@gmail.com>
Date: Tue, 20 Jul 2010 15:37:42 +0200
Message-ID: <4C45A6A6.6050000@gmail.com>

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.

Feedback is welcome :)

Received on Tuesday, 20 July 2010 06:37:42 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:25 UTC