W3C home > Mailing lists > Public > www-forms-editor@w3.org > January 2002

Re: Order of xforms:revalidate and xforms:recalculate

From: Jérôme Nègre <jerome.negre@e-xmlmedia.fr>
Date: Mon, 21 Jan 2002 09:46:06 +0100
Message-ID: <003501c1a258$30de6eb0$630aa8c0@fischer>
To: "Micah Dubinko" <MDubinko@cardiff.com>, <www-forms-editor@w3.org>
Since that paragraph hasn't changed, I think it's still a problem.

Please note that the suggested default processing doesn't take dependencies
between instances into account.

Regards,
Jérôme

----- Original Message -----
From: "Micah Dubinko" <MDubinko@cardiff.com>
To: "'Jérôme Nègre'" <jerome.negre@e-xmlmedia.fr>
Sent: Friday, January 18, 2002 9:09 PM
Subject: RE: Order of xforms:revalidate and xforms:recalculate


Could you double-check this against our 18-Jan spec, and if it's still a
problem, post a comment to www-forms-editor@w3.org?

Thanks!

.micah

-----Original Message-----
From: Jérôme Nègre [mailto:jerome.negre@e-xmlmedia.fr]
Sent: Thursday, December 20, 2001 12:41 AM
To: tvraman@almaden.ibm.com
Cc: www-forms@w3.org
Subject: Re: Order of xforms:revalidate and xforms:recalculate


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 Monday, 21 January 2002 03:47:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 10 June 2009 18:12:10 GMT