W3C home > Mailing lists > Public > public-xformsusers@w3.org > June 2018

Re: ACTION-2188: Reformulate embedded examples using signal.

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Wed, 20 Jun 2018 12:33:03 +0200
To: public-xformsusers@w3.org, "XForms Users Community Group Issue Tracker" <sysbot+tracker@w3.org>
Message-ID: <op.zkwkxdvmsmjzpq@steven-xps>
On Wed, 20 Jun 2018 12:23:29 +0200, Steven Pemberton  
<steven.pemberton@cwi.nl> wrote:

I briefly tried to do this, but frankly it was clumsy, and didn't match  
the ease with which you can do other things in XForms.

So, if there is a problem with using <submission/> as the method to return  
values from an embedded form, how about making an action to do it:

	<return ref="values"/>

<<<<

The return Element

This action returns values from an embedded form.

Common Attributes: Common, Events, Action Common

If the submitting form has not been embedded in another, or the embedding  
form has not supplied a receiving binding for submission results, then an  
xforms-action-error event with an error-type of return-error is dispatched.

Otherwise, an update is done if necessary, and the binding attributes  
evaluated to give a nodeset, which is returned to the embedding XForm, and  
is used to replace the node specified in the binding attribute of the  
control element in that form, as if by a submission with  
replace="instance" targetref="...".

Examples

<return ref="instance('result')"/>
<return ref="values[@selected=true()]"/>

>>>>

Question: should relevance trimming be done, as with submission?

Steven



> On Wed, 13 Jun 2018 15:22:16 +0200, XForms Users Community Group Issue  
> Tracker <sysbot+tracker@w3.org> wrote:
>
>> ACTION-2188: Reformulate embedded examples using signal.
>>
>> https://www.w3.org/2005/06/tracker/xforms/actions/2188
>>
>> Assigned to: Steven Pemberton
>>
>>
>>
>>
>>
Received on Wednesday, 20 June 2018 10:33:34 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 20 June 2018 10:33:35 UTC