[whatwg] [WF2] <select required>
zcorpan at hotmail.com
Tue Oct 3 17:32:27 PDT 2006
From: Robert <mail at robbiegee.com>
>On Mon, 02 Oct 2006 16:35:32 +0200, Simon Pieters <zcorpan at hotmail.com>
>Submitting an empty value may be wanted,
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?
>and since a select by definition is a list of predefined valid values, it
>would make little sense to prevent the user from selecting some of them.
In practice they are prevented today (with script). The most common way to
do this (from what I've seen) is to use "" as value for the first option,
and then check the value with script (either client side or server side,
although on the client side you could check for selectedIndex instead).
>However, I agree with the use case of the invalid starter value so users
>must consciously select a value they wanted instead of the default one.
So should there be a declarative way to express this?
More information about the whatwg