- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Wed, 29 Jan 2020 12:13:25 +0100
- To: public-xformsusers@w3.org, "XForms Users Community Group Issue Tracker" <sysbot+tracker@w3.org>
At the end of 5.4.9 Refresh (https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Refresh) [[[[ Notification events are dispatched with no defined ordering: [existing text:] 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. 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 controls. The events xforms-out-of-range and xforms-in-range must also be dispatched as appropriate to enabled controls. [end existing text] Finally an xforms-refresh-done event is dispatched. ]]]] [[[[ 13.3.x The xforms-refresh-done Event This notification event is dispatched once for each model, when a refresh has completed. Target: model Bubbles: Yes Cancelable: No Context Info: None ]]]] Steven
Received on Wednesday, 29 January 2020 11:13:31 UTC