Quoted below is some feedback basically asking for a way to:
a) make select not have a default value
b) show a placeholder when there's no default value
c) make picking a selection required for submission
Something like:
label
Country:
select placeholder=Select a country required=
On Fri, Oct 24, 2008 at 12:37 AM, Andy Lyttle [EMAIL PROTECTED] wrote:
On Oct 23, 2008, at 12:19 PM, Tab Atkins Jr. wrote:
Ultimately the display of the hint is, and should be, up to the UA, so that
non-full-featured devices can display things in a maximally helpful way to
the user. Within
On Fri, Oct 24, 2008 at 11:57 AM, Andy Lyttle [EMAIL PROTECTED] wrote:
On Oct 24, 2008, at 8:23 AM, Tab Atkins Jr. wrote:
So, pulling it all together, my proposal for a hinting ability on select
is thus:
select can have a @hint attribute, which takes a text value. If there
is no option
I just realized that there is existing support for using a first OPTION as a
non-selectable hint value. Instead of this:
select
option value=[[invalid]]Select one/option
option value=None of these/option
option value=love itLove It/option
option value=hate itHate It/option
/select
Of Weston Ruter
Sent: Friday, October 24, 2008 9:40 PM
To: [EMAIL PROTECTED]
Cc: Ian Hickson; Tab Atkins Jr.; Joao Eiras; Simon Pieters; Robert
Subject: Re: [whatwg] [WF2] select required
I just realized that there is existing support for using a first OPTION as a
non-selectable hint value
*Sent:* Friday, October 24, 2008 9:40 PM
*To:* [EMAIL PROTECTED]
*Cc:* Ian Hickson; Tab Atkins Jr.; Joao Eiras; Simon Pieters; Robert
*Subject:* Re: [whatwg] [WF2] select required
I just realized that there is existing support for using a first OPTION as
a non-selectable hint value. Instead
On Mon, 2 Oct 2006, Simon Pieters wrote:
The required= attribute doesn't apply to selects in the current
draft of WF2. As an author I'd expect it to apply to select.
I've seen a case where a select is used and the user is required to
change its value, as in:
select name=test
Many times I've set SELECT.selectedIndex to -1 to have the effect of an
invalid starter value; I think this is a case where the REQUIRED attribute
would make sense. If a SELECT has a REQUIRED attribute, and
SELECT.selectedIndex == -1, then the control would be considered invalid.
It would also
On Oct 23, 2008, at 5:31 AM, Ian Hickson wrote:
This use case is definitely something we want to consider, but I don't
think it's about required=. It's about an option in the select
being a
non-option (as it were). select by definition can't have nothing
selected. That's what it means.
The
On Thu, Oct 23, 2008 at 12:45 PM, Andy Lyttle [EMAIL PROTECTED] wrote:
On Oct 23, 2008, at 5:31 AM, Ian Hickson wrote:
This use case is definitely something we want to consider, but I don't
think it's about required=. It's about an option in the select being a
non-option (as it were).
On Oct 23, 2008, at 12:19 PM, Tab Atkins Jr. wrote:
Ultimately the display of the hint is, and should be, up to the UA,
so that non-full-featured devices can display things in a maximally
helpful way to the user. Within the context of a standard browser
on an ordinary computer, though, the
Well, the option element could be extended with a new attribute 'invalid'
which hold prevent that option to be selected.
Robert [EMAIL PROTECTED] escreveu:
On Mon, 02 Oct 2006 16:35:32 +0200, Simon Pieters [EMAIL PROTECTED]
wrote:
I've seen a case where a select is used and the user is
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
13 matches
Mail list logo
