On Wed, 04 Oct 2006 02:32:27 +0200, Simon Pieters <[EMAIL PROTECTED]> wrote:
Then don't mark the select as being required. Or do you mean that there are cases where the user has to change the value to ""? What would that be?
One case could be that an old web application is configured serverside to interpret an empty value as "none of the above". For the author, it would be risky to change this as opposed to just slapping on some added functionality for modern browsers on the client side.
So should there be a declarative way to express this?
I say yes, but I think "pattern" is a better candidate than "required", or as Joao Eiras suggested, marking certain options as "invalid" - or all of the above. - Robert Græsdal