- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Fri, 15 Jan 2021 14:41:14 +0000
- To: XForms <public-xformsusers@w3.org>
- Message-Id: <1610721558130.605817907.188484259@cwi.nl>
I just realised that there is a problem here: if send doesn't explicitly reference a <submission/>, then the first submission in document order from the model associated with the in-scope evaluation context is used. So that suggests that there is always a <submission/> element involved. Steven On Fri Jan 15 2021 14:44:47 GMT+0100 (Central European Standard Time), Steven Pemberton wrote: > One of the issues we discussed was where to dispatch submit-error and submit-done to if <send/> doesn't specify a <submission/> > One possible solution is to say > * <send/> operates as normal, using a <submission/> element; attributes on <send/> add to or override the equivalent attributes on the <submission/>. submission errors are, as always, dispatched to the <submission/> > * if a <send/> doesn't reference a <submission/>, then its attributes are used, but submission errors are ignored. > > In the latter case, if you still wish to catch submission errors, then use an empty <submission/> > > <submission id="s"> > <action ev:event="xforms-submit-error"> > ... > </action> > </submission> > ... > <send submission="s" ...> > > Steven > > --
Received on Friday, 15 January 2021 14:41:29 UTC