Re: Active submissions

This wouldn't work all that well because submissions can be performed by 
send actions, which can reside
anywhere.  The easiest place is in a DOMActivate handler of a trigger, of 
course, but a send can be done
in response to an event dispatched by an event dispatched by an event... 

Even the simple case of wanting to do a send preceded or followed by a few 
things like setting the focus
means that the trigger is logically connected to the submission but not in 
a way that allows the gray-out.

If we want to add this feature, perhaps we could make it a more generic 
feature that allows any UI control
to become non-active during the operation of a particular submission.

John M. Boyer, Ph.D.
Senior Product Architect/Research Scientist
Co-Chair, W3C XForms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com  http://www.ibm.com/software/

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer





"Steven Pemberton" <steven.pemberton@cwi.nl> 
Sent by: www-forms-request@w3.org
06/16/2006 10:44 AM

To
"www-forms@w3.org" <www-forms@w3.org>
cc

Subject
Active submissions







I have a form (and I'm sure many others have too) where the server takes a 
 
long time to return the results after a submission.

Users were getting confused about whether the submit had 'taken', so I 
added the necessary event handling to toggle feedback that the submit was 
being processed.

However, I think that there should be a low-cost default that makes it 
clear that something has happened, and I would like to propose that the 
spec states that all submit elements bound to a submission are in state 
'active' between xforms-submit and xforms-submit-done, so that you can use 
 
the CSS :active selector to style elements appropriately.

Steven Pemberton