W3C home > Mailing lists > Public > public-xformsusers@w3.org > March 2019

Re: select1

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Tue, 26 Mar 2019 15:54:15 -0700
Message-ID: <CAAc0PEVF03sK5F7vRoUY0b-psXkQdWeiD3egdJsfGvUhpsLm+w@mail.gmail.com>
To: Steven Pemberton <steven.pemberton@cwi.nl>
Cc: XForms <public-xformsusers@w3.org>
Interesting that HTML says:

   "A select element whose multiple attribute is not specified *must not*
have more than one descendant option element with its selected attribute
set." [1]

But what if it does? It appears the spec is silent on this.

HTML dropdowns in Chrome, specifically, select the last item if more than
one have the `selected` attribute set.

I think that our implementation only selects the first item with the given
value.

I think that we should specify that only one item is selected (that's what
the UI enforces anyway), and pick either first or last.

With `<select>`, there is an opportunity to select multiple items if they
have the same value, although the use case is not clear and user confusion
can ensue.

> <count>2 2</count>?

In my book that should behave the same as `<count>2</count>`.

-Erik

[1]
https://html.spec.whatwg.org/multipage/form-elements.html#the-option-element

On Tue, Mar 26, 2019 at 8:12 AM Steven Pemberton <steven.pemberton@cwi.nl>
wrote:

> <instance>
>     <data xmlns="">
>        <count>2</count>
>     </data>
> </instance>
>
> <select1 ref="count">
> <item><label>Un</label><value>1</value></item>
> <item><label>Deux</label><value>2</value></item>
> <item><label>One</label><value>1</value></item>
> <item><label>Two</label><value>2</value></item>
> </select1>
>
> What is correct behaviour? One label selected, both, or undefined?
>
> How about with <select>?
> How about with <count>2 2</count>?
>
> Steven
>
>
Received on Tuesday, 26 March 2019 22:54:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:37:51 UTC