W3C home > Mailing lists > Public > www-forms@w3.org > August 2002

RE: Naming: select1 vs. singleSelect

From: Dan G. Switzer, II <dswitzer@oar.net>
Date: Mon, 26 Aug 2002 10:31:32 -0400
To: <dagfinn.reiersol@opoint.com>, <www-forms@w3.org>
Message-ID: <001401c24d0d$46516c10$dc6112c7@dansnbk>

It would make much more since to me to have something like this:

<select min="" max="" />

Where "min" and "max" are optional attribute specifying the number of
options that can/must be selected. By default "min" would default to
zero and "max" would default to "unlimited." 

This would give the default behavior the same, but allow you to granular
control over how many items can/should be selected.


> -----Original Message-----
> From: www-forms-request@w3.org [mailto:www-forms-request@w3.org] On
> Of Dagfinn Reiersøl
> Sent: Monday, August 26, 2002 7:07 AM
> To: 'www-forms@w3.org'
> Subject: Re: Naming: select1 vs. singleSelect
> On Monday 26 August 2002 10:57, Kurt George Gjerde wrote:
> > The new <select/> (instead of selectMany) is also confusing since
> > current uses of the HTML select element is for selecting a single
> I prefer SelectMany because it is more descriptive. Why give something
> name
> which is harder than necessary to understand and remember, even though
> difference may be small?
> > And, what's the reason for having two select elements in the first
> place?
> > Can't there just be an attribute that says how many items that can
> > selected?
> Perhaps because there is a logical difference, both from the user's
> the
> developer's point of view.
Received on Monday, 26 August 2002 10:32:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:44 UTC