W3C home > Mailing lists > Public > public-xformsusers@w3.org > June 2018

Re: ACTION-2187: Suggest text for value change events etc in model.

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Wed, 20 Jun 2018 12:12:22 +0200
To: public-xformsusers@w3.org, "XForms Users Community Group Issue Tracker" <sysbot+tracker@w3.org>
Message-ID: <op.zkwjywx6smjzpq@steven-xps>
Seems to be fairly straightforward:



13.3.3 The xforms-value-changed Event

This notification event is dispatched during a refresh after a change to  
an instance data node bound to a core control or a bind element.

Target:  Core Controls|bind Bubbles: Yes Cancelable: No Context Info: None


For controls with incremental=true, it is not defined how often this event  
is fired. Implementations should optimize processing (for instance not  
flashing the entire screen for each character entered, etc.).



5.4.9 Refresh

All UI Expressions are re-evaluated as necessary, and the user interface  
is updated to reflect the state of the model, including:
  * current values,
  * model item properties: validity, relevance, read-write, and  
  * the proper number of, and content for, repeat objects.

Notification events are dispatched:
  * If a bound value has become non-relevant since the last refresh, the  
xforms-disabled event is dispatched to the value's bound controls; if a  
bound value has become relevant, the xforms-enabled event is dispatched.
  * If a bound value has changed since the last refresh, then the  
xforms-value-changed event is dispatched to the value's enabled bound  
controls, and bind elements.
  * If any other model item properties of a bound value have changed since  
the last refresh, the appropriate notification events  
(xforms-optional/xforms-required, xforms-readwrite/xforms-readonly,  
xforms-valid/xforms-invalid) are dispatched to the value's enabled bound  
  * The events xforms-out-of-range and xforms-in-range must also be  
dispatched as appropriate to enabled controls.

There is no defined ordering for the events.

However, this immediately raised some issues that are worth discussing.

1) Different notification events are targeted to different places:

xforms-value-changed to Core Controls
xforms-valid xforms-invalid xforms-readonly xforms-readwrite  
xforms-required  xforms-optional xforms-enabled xforms-disabled
	to Core Controls|group|switch

2) Since the second group of events are the result of properties defined  
in the model, maybe we should be able to catch those on binds as well.

3) We use the phrase "bound value" several times in the spec, without  
formally defining it. We should.


On Wed, 13 Jun 2018 15:18:13 +0200, XForms Users Community Group Issue  
Tracker <sysbot+tracker@w3.org> wrote:

> ACTION-2187: Suggest text for value change events etc in model.
> https://www.w3.org/2005/06/tracker/xforms/actions/2187
> Assigned to: Steven Pemberton
Received on Wednesday, 20 June 2018 10:12:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:37:49 UTC