W3C home > Mailing lists > Public > public-forms@w3.org > April 2014

Re: ACTION: Steven to implement @label spec text

From: Steven Pemberton <Steven.Pemberton@cwi.nl>
Date: Wed, 09 Apr 2014 15:00:12 +0200
To: "Steven Pemberton" <Steven.Pemberton@cwi.nl>, "Erik Bruchez" <erik@bruchez.org>
Cc: "Forms WG" <public-forms@w3.org>
Message-ID: <op.xd1vqmdcsmjzpq@steven-ux21a>
On Wed, 09 Apr 2014 07:47:47 +0200, Erik Bruchez <erik@bruchez.org> wrote:

>> 2. Specify that an element may have both, but the attribute takes  
>> precedence
>> (or do we forbid both, and require one or the other?). Of the core  
>> controls,
>> only on <output> is the label optional. The label attribute may also be  
>> an
>> AVT.
>
> All of @label, @help, @hint, and @alert are AVTs, right?

Right.

>
>> 3. group, dialog, choices, item, itemset only have <label> (no help  
>> hint and
>> alert)
>
> (Different topic, but it can make sense to have hint/help on
> item/itemset, especially for the full appearance.)

Let's discuss.

Steven

>> @value @copy: these are both expressions. Note, that means @label is an  
>> AVT,
>> and @value is not. Check that you agree with the following examples:
>
>> <select model="cone" ref="my:order" label="Flavors">
>>   <itemset model="flavors" ref="my:flavor" label="{my:description}"
>> copy="my:description"/>
>> </select>
>
> That seems reasonable.
>
>> <select1 ref="..." label="Gender">
>>    <item label="male">m</item>
>>    <item label="female">f</item>
>> </select>
>
> We had suggested supporting this at some point. It wasn't too keen on
> it initially as that was the opposite of HTML's <option>, but the
> benefit is that the syntax is lighter than adding a nested <value>
> element.
>
> -Erik
Received on Wednesday, 9 April 2014 13:00:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:14:10 UTC