- From: David Landwehr <david.landwehr@solidapp.com>
- Date: Tue, 04 Apr 2006 14:27:25 +0200
- To: Allan Beaufour <beaufour@gmail.com>
- Cc: www-forms@w3.org
> I'm not quite following the usefulness in your example though. You
> start by "teasing" the submission action, before submitting to it? :)
>
>
Just to making sure the server is awoke and alert before sending the
real stuff ;)
No the idea is that if you use an input and a submission to populate
e.g. a select1 then you would have something like:
<xforms:select1 ref="populated">
<xforms:itemset nodeset=""
<xforms:input ref="prefix" incremental="true">
<xforms:action ev:event="xforms-value-changed">
<xforms:cancel submission="s1"/>
<xforms:send submission="s1"/>
This wouldn't work probably without the cancel since there can only be
one submit pr. submission element on the way, which might make the
submission miss the changes to the input done between the last
xforms-submit, xforms-submit-done.
Best regards,
David
--
--------------------------------------------
David Landwehr (david.landwehr@solidapp.com)
Chief Executive Officer, SolidApp
Web: http://www.solidapp.com
Office: +45 48268212
Mobile: +45 24275518
--------------------------------------------
Received on Tuesday, 4 April 2006 12:27:31 UTC