W3C home > Mailing lists > Public > public-forms@w3.org > January 2010

Test 11.2.a is broken

From: John Boyer <boyerj@ca.ibm.com>
Date: Tue, 19 Jan 2010 11:54:24 -0800
To: public-forms@w3.org
Message-ID: <OFF5170375.03CBE26E-ON882576B0.006CD344-882576B0.006D5A53@ca.ibm.com>
The test attempts to dispatch two xforms-submit events one right after the 
other to the same submission. 

The test then claims you should *not* see an xforms-submit-error.

This may have been true when submissions were assumed to be synchronous by 
default.  In that case, it is true you wouldn't see the error but it is 
also true that the test wouldn't be testing what it is supposed to be 
testing.

The test is supposed to be a test of failure of the second concurrent 
submit requested on the same submission element.

In XForms 1.1, the default submission mode is asynchronous.  It seems in 
that case that you might see an xforms-submit-error on the second 
submission if the first one has not completed.  This would be a violation 
of what the test claims should happen but it would be a proper test of 
what the test is supposed to be testing.

The problem with it being a proper test, though, is that the first 
submission is by no means guaranteed to take long enough to ensure that 
the second submission will fail.

One way to test is to have the submission point to a bogus resource and 
count on the browser timeout to create the needed delay.

Let's talk about how to fix this test.

John M. Boyer, Ph.D.
STSM, Lotus Forms
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com 

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed: 
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw
Received on Tuesday, 19 January 2010 19:54:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 October 2013 22:06:53 UTC