W3C home > Mailing lists > Public > www-forms@w3.org > December 2001

Re: Order of xforms:revalidate and xforms:recalculate

From: Jérôme Nègre <jerome.negre@e-xmlmedia.fr>
Date: Thu, 20 Dec 2001 09:41:29 +0100
Message-ID: <003201c18932$1f5181d0$630aa8c0@fischer>
To: <tvraman@almaden.ibm.com>
Cc: <www-forms@w3.org>
To sum up, the default processing for chapter 11.3.6 should be :

1. If the value from the form control meets all validity constraints:
    a- It is reflected in the instance data.
    b- Event recalculate has been dispatched to element model.
    c- Event revalidate has been dispatched to element model.
If not,
    a- The instance data remains as it was before processing this event.
    b- The form control is marked as invalid.
2. Event refresh has been dispatched to element model.

Is this correct ?


----- Original Message -----
From: "T. V. Raman" <tvraman@almaden.ibm.com>
To: "Jérôme Nègre" <jerome.negre@e-xmlmedia.fr>
Cc: <www-forms@w3.org>
Sent: Wednesday, December 19, 2001 11:35 PM
Subject: Order of xforms:revalidate and xforms:recalculate


The thought underlying the sequence is:

You type a value into a field --
first you need to check if that is valid.

Once you've checked it is valid, you run the recalculate to
update fields that may depend on the one you filled in.
That in turn may change fields --hence the revalidate after
calculate.

Thus, depending on how the constraints are authored, it
might be possible to type in a value that is "locally valid"
but turns out to be invalid with respect to the form.
Received on Thursday, 20 December 2001 03:42:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:21:50 GMT