W3C home > Mailing lists > Public > public-forms@w3.org > June 2007

More on xforms:select storage

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Fri, 01 Jun 2007 13:14:38 -0700
Message-ID: <46607E2E.5050306@orbeon.com>
To: public-forms@w3.org
CC: www-forms-editor@w3.org

All,

Assume again an instance containing the following:

   <value>vanilla strawberry elephant</value>

and the following xforms:select control:

     <xforms:select ref="value">
         <xforms:label>Flavors</xforms:label>
         <xforms:item>
             <xforms:label>Chocolate</xforms:label>
             <xforms:value>chocolate</xforms:value>
         </xforms:item>
         <xforms:item>
             <xforms:label>Vanilla</xforms:label>
             <xforms:value>vanilla</xforms:value>
         </xforms:item>
         <xforms:item>
             <xforms:label>Strawberry</xforms:label>
             <xforms:value>strawberry</xforms:value>
         </xforms:item>
         <xforms:item>
             <xforms:label>Hazelnut</xforms:label>
             <xforms:value>hazelnut</xforms:value>
         </xforms:item>
     </xforms:select>

Now it seems that the control will be out of range if I guess enough
from the spec.

Now what happens if I select "hazelnut" from the control?

1. First, is the control functional at all if out of range? I don't
    read otherwise in the spec.

2. If it is functional, then does it append the "halzenut" value to
    the sequence of values, or does it replace the current value
    entirely? I.e. which of the following does it produce:

    a. <value>vanilla strawberry elephant hazelnut</value>
    b. <value>vanilla strawberry hazelnut</value>
    c. (any other possibility?)

-Erik

-- 
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/
Received on Friday, 1 June 2007 21:10:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 October 2013 22:06:43 UTC