W3C home > Mailing lists > Public > www-forms-editor@w3.org > May 2007

Value changes upon instance replacement

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Fri, 18 May 2007 17:16:25 +0200
Message-ID: <464DC349.4090005@orbeon.com>
To: public-forms@w3.org
CC: www-forms-editor@w3.org


At the moment, I don't think this is clearly specified to happen.

Use case:

1. <xforms:input ref="name">

2. The instance containing "name" is replaced.

3. Section 11.2 specifies that a refresh must take place. However, no
    node of the new instance is marked as having changed as I
    understand it. 4.3.4 says "If the value of an instance data node
    was changed, then the node must be marked for dispatching the
    xforms-value-changed event.". But in this case, the value of the
    node hasn't changed because the node is just freshly created from
    the instance replacement.

4. Consequence: no xforms-value-changed is fired.

This behavior is very non-intuitive because you can replace an
instance under controls' feet and while the control may update their
values in the UI, no xforms-value-changed is fired.

This means that you cannot reliably use events to determine if the
value of a control has changed or not. I think that this should be
possible, or the usefulness of value-changed-events is greatly


Orbeon Forms - Web Forms for the Enterprise Done the Right Way
Received on Friday, 18 May 2007 15:16:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:38:09 UTC