As I see it, list is perfectly fine the way it was designed but it could be
applied to select elements, thus enabling feeding options to a dropdown
externally, thus enabling a way to reuse options in dropdowns (without
redundant nodes).

I am building long immigration forms for USCIS and, for example, a very
common field is Country. It is asked several times even in the same page
(for the address of birth, address of residence, address of your relative,
etc...). Relative kind is another example.

So I think it makes sense to have a single <datalist> and then have

<select name="" list="countries"></select>
<select name="" list="countries"></select>

On Sun, May 18, 2014 at 1:41 PM, Anne van Kesteren <> wrote:
> On Sun, May 18, 2014 at 6:34 PM, Luis Farzati <> wrote:
> > Sorry if this has been discussed already, but I wanted to ask you guys
> > you have considered making the list attribute available for selects.
> I don't think so. What would the use case be?
> --

Reply via email to