- From: Aaron Reed <aaronr@us.ibm.com>
- Date: Wed, 8 Feb 2006 17:19:58 -0600
- To: www-forms@w3.org
- Message-ID: <OFC586126C.73F41D5A-ON8625710F.007F544A-8625710F.007FFB6E@us.ibm.com>
Hi, I'm seeing different behaviors in different processors. And the spec (2nd edition) can be interpreted multiple ways. Assume I have an input and a range bound to the same node of type xsd:integer with an initial value of 1. I then, via the input, change the value to -1. That should generate a xforms-out-of-range, right? So how about if I now change the value to -2? Should this generate another xforms-out-of-range, or since the item is out of range already, should it not generate a out of range? And how about xforms-in-range? If something is in range, like a value of 1, and the value is changed to 2. Will that generate a xforms-in-range? So I guess the short question is, should in and out of range event only be generated when the state changes or every time? Novell does it every time for both in and out of range. Mozilla only when the state changes. When I tried it in formsPlayer, I didn't get any popup. Thanks, --Aaron
Received on Thursday, 9 February 2006 14:38:10 UTC