- From: Micah Dubinko <MDubinko@cardiff.com>
- Date: Fri, 4 Oct 2002 16:58:28 -0700
- To: "'bhanu'" <bhanu_k@hotmail.com>, www-forms@w3.org
>So if I am reading this correctly, the processor should treat UI controls differently when a UI Control does not have a binding expression vs. when a UI control does have a binding expression but points to a node that does not exist. I believe that is correct. Anyone feel free to jump in if I'm mistaken. .micah -----Original Message----- From: bhanu [mailto:bhanu_k@hotmail.com] Sent: Wednesday, October 02, 2002 2:45 PM To: www-forms@w3.org Subject: UI Control binding Expression As per Section 4.2.5 (xforms-form-control) If the instance referenced on the form control existed when the first xforms-form-control-initialize event was processed 1. The binding expression is evaluated to ensure that it points to a node that exists. If this is not the case then the form control should behave in the same manner as if it had bound to a model item with the relevant model item property resolved to false. As per Section 8.1.8 (trigger Control) Data Binding Restrictions: Binds to any node. This form control does not directly interact with form data, but is affected by model item properties of the bound node, thus binding attributes are not required. So if I am reading this correctly, the processor should treat UI controls differently when a UI Control does not have a binding expression vs. when a UI control does have a binding expression but points to a node that does not exist. Regards
Received on Friday, 4 October 2002 19:58:34 UTC