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

Re: in-range/out-of-range question

From: Sebastian Schnitzenbaumer <schnitz@demaledetti.net>
Date: Fri, 10 Feb 2006 12:53:49 +0100
Message-ID: <001001c62e38$abba08e0$7da0e20a@sebastia7b6f41>
To: "Aaron Reed" <aaronr@us.ibm.com>
Cc: <www-forms@w3.org>

Aaron, all,

have you been helped with your question yet?

I personally would say that firing once, ie. only
when the state changes seems better, but of course
would want to hear other opinions and settle on
this issue in consensus as a errata.

The reason why I think firing once might be the
better option is not so much from a processor
perspective, but more useability-wise:

If a user deliberately enters values out of range,
it is enough to inform him once, informing him
everytime he changes his values outside of the
range, always gives this impression of software
that is too restrictive, ie. my car beeps for ages
every time when I put on no seat belt even if I
just move in the slowest possible speed at a gas
station for just a couple of meters... informing me
once would have been just fine here.

Of course the form author can listen to the
out of range event and pop up a permanent
message by e.g. triggering a switch/case toggle
for the time being out of range, so permanently
informing the user is still possible authoring-wise
even if the event is not dispatched every time.

- Sebastian

----- Original Message ----- 
From: Aaron Reed
To: www-forms@w3.org
Sent: Thursday, February 09, 2006 12:19 AM
Subject: in-range/out-of-range question


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.

Received on Friday, 10 February 2006 11:57:22 UTC

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