All, Let's assume that an instance is submitted with replace="instance". The spec (errata) says: "[...] all of the internal instance data ... is replaced with the result. Once the XML instance data has been replaced, the rebuild, recalculate, revalidate and refresh operations are performed on the model, without dispatching events to invoke those four operations. Submit processing then concludes after dispatching xforms-submit-done." What is the rationale behind the "no-event" clause? If a control is bound to a node whose value changes because the instance is entirely replaced, wouldn't it make sense for events to be sent by that control upon refresh? At the very least, shouldn't this be an option? Thanks for your opinion, -ErikReceived on Wednesday, 10 August 2005 21:48:45 UTC
This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:15 UTC