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

Re: ACTION-2292: Specify merge of send and load.

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Fri, 18 Dec 2020 13:51:23 +0100
To: public-xformsusers@w3.org, "XForms Users Community Group Issue Tracker" <sysbot+tracker@w3.org>, "Steven Pemberton" <steven.pemberton@cwi.nl>
Message-ID: <op.0vtnbxqesmjzpq@steven-xps13>
I should add two questions to this:

- Do we want to add a @submission to <load/>?
- load has xforms-load-error rather than submit-error; anything special  
need to be done?


On Fri, 18 Dec 2020 13:44:30 +0100, Steven Pemberton  
<steven.pemberton@cwi.nl> wrote:

> So here is my proposal:
> The <submission> element carries all its usual attributes.
> <send/> may also carry any attribute from <submission/>
> 1) If it has a @submission attribute, the attributes on <send/> are  
> added to or replace those on the <submission/>, and the submission  
> proceeds as normal. Events are sent to the <submission/> element.
> 2) If it doesn't have a @submission attribute, the send element does all  
> the work of the submission, and events are sent to it.
> <load/> has new attributes @replace @targetref
>          <load resource="x" replace="all"/>
> is equivalent to
> 	<send serialization="none" resource="x" replace="all"/>
> What to do with <load ref="y"/>?
> I note that <submission resource="x" replace="all"/> says:
> all: the event xforms-submit-done may be dispatched with appropriate  
> context information, and submit processing concludes with the entire  
> containing document being replaced with the returned body.
> while <load resource="x"/> has:
>     If the result is an empty sequence, an xforms-load-error is  
> dispatched to the load element.
> How do we deal with that difference?
> Do we want to allow all submission attributes on <load/> as well?
> Steven
Received on Friday, 18 December 2020 12:51:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 18 December 2020 12:51:37 UTC