xforms-disabledAdded by IBM on October 10, 2012 | Version 1 (Original)
|Occurs when an data node changes its state from relevant to non-relevant, or when a data node that is not relevant changes value and remains non-relevant.
This event is triggered on the XForms control bound to that node.
Available In xforms:input, xforms:output, xforms:range, xforms:secret, xforms:select, xforms:select1, xforms:submit, xforms:textarea, xforms:trigger, xforms:upload
Example This example shows a label item that displays the total for a purchase order. If the total is less than 100, then the data node becomes non-relevant and the xforms-disabled event is triggered. In this case, the event triggers an xforms:message action that explains that the total is too low.
The following bind sets the minimum value of the po/total node in the data model to be 100:
The following code defines the label that displays the total:
<xforms:bind nodeset="po/total" relevant=". > 100"/>
<xforms:message ev:event="xforms-disabled" level="modal"
>Values less than $100 should be paid from petty cash.</xforms:message>
- The order in which user interface events are processed is indeterminate. This means you cannot rely on them processing in a particular order.