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

xforms-refresh

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Fri, 18 Nov 2016 20:59:28 +0100
To: "public-xformsusers@w3.org" <public-xformsusers@w3.org>
Message-ID: <op.yq425esismjzpq@steven-aspire-s7>
https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_xforms-refresh_Event

"If the xforms-value-changed event is marked for dispatching, then all of  
the appropriate model item property notification events must also be  
marked for dispatching (xforms-optional or xforms-required,  
xforms-readwrite or xforms-readonly, and xforms-enabled or  
xforms-disabled)."

However, xforms-recalculate goes to a lot of trouble to only mark such  
events for dispatch if the property has changed.

Is there a use case for sending (xforms-optional or xforms-required,  
xforms-readwrite or xforms-readonly, and xforms-enabled or  
xforms-disabled) when the value has changed, but the property hasn't?

Steven
Received on Friday, 18 November 2016 20:00:07 UTC

This archive was generated by hypermail 2.3.1 : Friday, 18 November 2016 20:00:07 UTC