W3C home > Mailing lists > Public > www-forms@w3.org > September 2009

Re: Regarding Test 8.1a

From: John Boyer <boyerj@ca.ibm.com>
Date: Tue, 29 Sep 2009 11:08:08 -0700
To: Erik Johnson <erikj@ca.ibm.com>
Cc: "www-forms@w3.org" <www-forms@w3.org>
Message-ID: <OFECBD582A.7ABEEB96-ON88257640.00638958-88257640.0063A182@ca.ibm.com>
Actually, the xf:label at the top of the form describes what would 
constitute a manually executed pass of the test of navindex.
This label would also have to change to reflect the change in the navindex 
attribute values.

Cheers,
John M. Boyer, Ph.D.
STSM, Interactive Documents and Web 2.0 Applications
Chair, W3C Forms Working Group
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





From:
Erik Johnson/Ottawa/IBM@IBMCA
To:
www-forms@w3.org
Date:
09/29/2009 11:02 AM
Subject:
Regarding Test 8.1a




Hey all, 

To be more complete in the testing of the navindex and the access keys in 
Xforms the navindex order must change. 

Currently the test is testing the navidex with the navindex's appearing in 
build order. This prevents the test from truly exploiting whether or not 
the mark-up has successfully navigated to the desired navidex unless the 
following happens: 

- Input 1 changed to nav index 2. 
- Input 2 keeps navindex 1. 
- Input 3 changed to navindex 3. 

By following this navindex order we can be assured that the navindex is 
opposite the build order in every case and the XForms test will reveal any 
true failures. 

An update form appears below. 

Thanks, 

Erik 
[attachment "8.1.a.xhtml" deleted by John Boyer/CanWest/IBM] 
Received on Tuesday, 29 September 2009 18:09:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:22:17 GMT