- From: Klotz, Leigh <Leigh.Klotz@xerox.com>
- Date: Tue, 11 Apr 2006 17:01:44 -0700
- To: "Allan Beaufour" <beaufour@gmail.com>
- Cc: <www-forms@w3.org>
Maybe I'm wrong but I thought that xforms-value-changed could be sent more than once per value change, or even if the value didn't change. (I've kind of filed the unreliable bit on it...) -----Original Message----- From: Allan Beaufour [mailto:beaufour@gmail.com] Sent: Tuesday, April 11, 2006 3:27 AM To: Klotz, Leigh Cc: www-forms@w3.org Subject: Re: Cancel a submission in progress On 4/7/06, Klotz, Leigh <Leigh.Klotz@xerox.com> wrote: > On my point 3, xforms-value-changed may occur more frequently than > desired if I read the rec correctly. How's that? > Did you think that group/action[@ref='xyz' & > @event='xforms-enabled]/load would be wrong? It seems to be the > closest to the author's intent, as the relevance of 'xyz' can be set > with bind/@relevant by the form author. Using > output[@event='xforms-value-changed'/load limits the control to a > single instance node, which means the determination of the condition > to do redirect is back on the instance document generating side > (server), and if that's the case we might as well just have the server > calculate the whole URI. Good point. Relevant might be more suited. -- ... Allan
Received on Wednesday, 12 April 2006 00:02:04 UTC