W3C home > Mailing lists > Public > public-xformsusers@w3.org > December 2016

refresh vs xforms-model-construct-done

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Thu, 01 Dec 2016 15:20:07 +0100
To: XForms <public-xformsusers@w3.org>
Message-ID: <op.yrsp3thdsmjzpq@steven-aspire-s7>
It seems to me that the definition of user interface construction needs to  
be tighter, since for example it nowhere says that the UI should reflect  
the state of validity. UI construct does not do a refresh.

Revalidate:
https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Revalidate

"Note: Since model initialization excludes doing a refresh and discards  
event notification marks, controls bound to invalid nodes do not receive  
an initial xforms-invalid event."

Refresh:
https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Refresh

"The user interface is updated to reflect the state of the model,  
including:
* current values
* validity and the other model item properties (required, readonly and  
relevant).
* the proper number of, and content for, repeat objects."

User Interface Initialization (default action of model-construct-done  
(https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_xforms-model-construct-done_Event)

https://www.w3.org/community/xformsusers/wiki/XForms_2.0#User_Interface_Initialization

"For each control:
* The user interface for the control is created and initialized.
...
if the control has a Single Item Binding, it is evaluated; if the result  
is an empty sequence then the control is non-relevant; if the result is an  
atomic value, the control is readonly."

Steven
Received on Thursday, 1 December 2016 14:20:53 UTC

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