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

Action: Triage of Firefox and EMC implementation Reports

From: Keith Wells <wellsk@us.ibm.com>
Date: Fri, 9 Jan 2009 11:22:42 -0500
To: Forms WG <public-forms@w3.org>
Message-ID: <OF9196B8C1.6E0F3563-ON87257538.00716E12-85257539.0059F83A@us.ibm.com>


Triage report for tests NOT Passing in the Firefox and EMC XForms 1.1
implementation reports

Action: Analyze the Firefox and EMC implementation reports to find the
failing tests and feature areas that are common in both reports.

Purpose:  For every successful test case, we can feel fairly confident
there is an implementation for the area of the spec the test case covers.
But if the implementation reports share common failing tests, then the
XForms WG needs to understand if these failures reflect unimplemented
features of the XForms 1.1 specification or some other concern ( incorrect
test case,  documentation error, etc) so we can design a course of action
(e.g. ask implementers to add features, etc) for a resolution.

Results:
These results are the common failing tests from analyzing the Firefox and
EMC XForms 1.1 implementation reports.

>From chapter 3:
3.3.1.c3 multiple schemas in a single namespace (
http://www.w3.org/TR/xforms11/#structure-model)
"This case has more than one schema with the same namespace declaration. An
unspecified error must occur. " tests "there is a limit of one Schema per
namespace declaration"

>From chapter 4:
4.5.2.a xforms-compute-exception (
http://www.w3.org/TR/xforms11/#evt-computeExceptionhttp://www.w3.org/TR/xforms11/#evt-computeException
)
4.5.3.a xforms-link-error (http://www.w3.org/TR/xforms11/#evt-linkError)
4.5.4.a xforms-link-exception (
http://www.w3.org/TR/xforms11/#evt-linkException)
4.5.5.a xforms-output-error event (
http://www.w3.org/TR/xforms11/#evt-output-error)
4.5.7.a xforms-version-exception (
http://www.w3.org/TR/xforms11/#evt-versionException)
4.6.3.b event sequencing for select/select1 controls without
incremental="true" (http://www.w3.org/TR/xforms11/#sequence-for-select)

>From chapter 5:
5.2.7.b card-number datatype - credit card example (
http://www.w3.org/TR/xforms11/#dt-card-number)

>From chapter 6:
6.1.7.a p3ptype property (http://www.w3.org/TR/xforms11/#model-prop-p3ptype
)

>From chapter 7,
7.5.a error in modal item property causes an xforms-compute-exception (
http://www.w3.org/TR/xforms11/#expr-lib)
7.5.b error not in modal item property causes an xforms-binding-exception (
http://www.w3.org/TR/xforms11/#expr-lib)
* working in FF2/3 now 7.6.2.a is-card-number() function (
http://www.w3.org/TR/xforms11/#fn-is-card-number)
7.10.3.b id() function with xml:id (http://www.w3.org/TR/xforms11/#fn-id)
7.10.3.c  id() function with xsi:type (http://www.w3.org/TR/xforms11/#fn-id
)
7.11.2.a event() function with binding property (
http://www.w3.org/TR/xforms11/#fn-event)

>From chapter 10:
10.4.a delete action using context attribute (
http://www.w3.org/TR/xforms11/#action-delete)
10.4.b delete action using context and bind attributes (
http://www.w3.org/TR/xforms11/#action-delete)
10.4.d delete action using at attribute (
http://www.w3.org/TR/xforms11/#action-delete)
10.4.f delete action and repeat element (
http://www.w3.org/TR/xforms11/#action-delete)
10.4.g delete action with xforms-delete event (
http://www.w3.org/TR/xforms11/#action-delete)
10.6.1.b case element child of the toggle element precedence testing (
http://www.w3.org/TR/xforms11/#action-toggle-case)

>From chapter 11:
11.2.d xforms-submit with empty instance data and required attribute (
http://www.w3.org/TR/xforms11/#submit-evt-submit)
* working in FF2/3 now 11.5.b accessing context information for
xforms-submit-error event (
http://www.w3.org/TR/xforms11/#submit-evt-submit-error)
11.7.1.a method element with value attribute (
http://www.w3.org/TR/xforms11/#submit-method-elem)
11.8.c header element of submission element (
http://www.w3.org/TR/xforms11/#submit-header)
11.9.m mailto Post as a submission option (
http://www.w3.org/TR/xforms11/#submit-options)
11.9.p mailto multipart-post as a submission option (
http://www.w3.org/TR/xforms11/#submit-options)
11.9.q mailto form-data-post as a submission option (
http://www.w3.org/TR/xforms11/#submit-options)
11.9.r mailto urlencoded-posts as a submission option (
http://www.w3.org/TR/xforms11/#submit-options)
11.9.4.a delete submission method (
http://www.w3.org/TR/xforms11/#submit-delete)
11.9.4.b delete submission method deletes a file (
http://www.w3.org/TR/xforms11/#submit-delete)
* working in FF2/3 now 11.9.8.a serialization as
application/x-www-form-urlencoded (
http://www.w3.org/TR/xforms11/#serialize-urlencode)
11.10.a submission response with invalid target (
http://www.w3.org/TR/xforms11/#submit-data-replacement)
11.10.b submission response with target receiving text (
http://www.w3.org/TR/xforms11/#submit-data-replacement)
11.11.3.a SOAP HTTP binding with get method (
http://www.w3.org/TR/xforms11/#SOAP-HTTP-Binding)
* working in FF2 now11.11.3.c SOAP HTTP binding (
http://www.w3.org/TR/xforms11/#SOAP-HTTP-Binding)
11.11.3.d SOAP HTTP binding with get method and encoding attribute  (
http://www.w3.org/TR/xforms11/#SOAP-HTTP-Binding)
11.11.3.e SOAP HTTP binding with post method and encoding attribute (
http://www.w3.org/TR/xforms11/#SOAP-HTTP-Binding)

Keith
Received on Friday, 9 January 2009 16:23:38 UTC

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