W3C home > Mailing lists > Public > www-forms@w3.org > April 2006

events for select/select1

From: Aaron Reed <aaronr@us.ibm.com>
Date: Sat, 22 Apr 2006 16:54:48 -0500
To: www-forms@w3.org
Message-ID: <OF13D48E45.65AD0642-ON87257158.0076B19F-86257158.0077CCC4@us.ibm.com>


I'm finding some inconsistencies between the different implementations and
I was wondering what the 'correct' answer is for this particular scenario.
Assume that I have a form with a select, select1 and a output all bound to
the same instance data node.  The select and select1 both contain identical
sets of items (Vanilla, Chocolate, Strawberry and Cherry Berry).  The
initial selection is 'Vanilla'.  If I now select 'Cherry Berry' from the
select1, from reading the spec the event order that I should expect for the
select1 is:

1) xforms-deselect for the Vanilla item
2) xforms-select for the Cherry Berry item
3) xforms-value-changed for the select1.

But what about the other controls?

   Should the Vanilla item in the select get a xforms-deselect?
   Should the Cherry Berry item in the select get a xforms-select?
   If these two are true, is it incorrect if the output gets a
   xforms-value-changed event before the items in the select get their
   xforms-deselect and xforms-select?  How about if the output gets the
   xforms-value-changed before the select1's items get xforms-deselect and

So in short I guess I'm wondering if xforms-select/deselect should be
generated on items that weren't physically selected/deselected by the user?
And are the event sequences in the spec guarenteed across the whole form
(all selects/deselects fire on the form before any value-changed events
fire) or are the event sequences only guarenteed on the controls that
receive them (independent of the other controls)?

Received on Sunday, 23 April 2006 00:21:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:17 UTC