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

Re: Test 10.8.e needs work

From: Charles F Wiecha <wiecha@us.ibm.com>
Date: Fri, 12 Feb 2010 14:46:11 -0500
To: John Boyer <boyerj@ca.ibm.com>
Cc: public-forms@w3.org
Message-ID: <OF8FF5CA67.D64F5E52-ON852576C8.006C757E-852576C8.006C9982@us.ibm.com>

As in 10.8.f I can't test this on Ubiquity and with the FF extension given
bugs in XML events and xf:dispatch respectively...but anybody with another
implementation is welcome/asked to provide feedback.  Thanks, Charlie

(See attached file: W3C-10.8.e.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:       02/04/2010 11:09 AM                                                                                            
  Subject:    Test 10.8.e needs work                                                                                         
  Sent by:    public-forms-request@w3.org                                                                                    

Test  10.8.e purports to test the dispatch of a cancelled event.

The ev:event attribute was placed on the model element, not on the action
element that shows the message proving that the event was dispatched.  So,
the test requires that one should *not* see a message for the custom-event,
but the reason you don't see it is that the event attributes are incorrect.

The ev:event attribute needs to be attached to the action element within
the model.

The model also has no instance, which is required, so I would not expect
this form to work.

However, we already have a test 10.8.d that tests dispatching a custom
event.  This test purports to test a cancelled event, i.e. one with a and
ev:defaultAction of cancel.  However, the test assumes that cancelling the
default action would cause the event bubble phase not to happen. The test
needs to use stopPropagation instead.  Then, another action handler needs
to be added to observe the parent of the event target instead.

So, I think this test should change by
1) adding an instance with an ID
2) targeting the custom event at the instance, not the model
3) attaching the ev:event and stopPropagation on the xforms action in the

Then, we can claim that you shouldn't see the message.

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:46:46 UTC

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