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

Re: Test 11.2.a is broken

From: Charles F Wiecha <wiecha@us.ibm.com>
Date: Fri, 12 Feb 2010 14:48:58 -0500
To: John Boyer <boyerj@ca.ibm.com>
Cc: public-forms@w3.org
Message-ID: <OF84C24595.FCFEEFC1-ON852576C8.006CA843-852576C8.006CDA74@us.ibm.com>

Updated to use Leigh's new timout features on xformstest.org...Charlie

(See attached file: W3C-11.2.a.xhtml)

Charles Wiecha
Multichannel Web Interaction
IBM T.J. Watson Research Center
P.O. Box 704
Yorktown Heights, N.Y.  10598
Phone: (914) 784-6180, T/L 863-6180, Cell: (914) 282-3483

  From:       John Boyer <boyerj@ca.ibm.com>                                                                                 
  To:         public-forms@w3.org                                                                                            
  Date:       01/19/2010 03:27 PM                                                                                            
  Subject:    Test 11.2.a is broken                                                                                          
  Sent by:    public-forms-request@w3.org                                                                                    

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

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:

(image/gif attachment: graycol.gif)

(image/gif attachment: ecblank.gif)

Received on Friday, 12 February 2010 19:49:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:48:39 UTC