W3C Tests 8.2.1.a through 8.2.2.c have xf:input disabled

[GoogleCodeExporter]

The following tests have the xf:input disabled, when it should not be:

8.2.1.a
8.2.1.b
8.2.1.c
8.2.2.a
8.2.2.b
8.2.2.c

This means 8.2.1.{a,b,c} now outrightly fail since no input is seen, and 
8.2.2.{a,b,c} fail depending on the way you look at it.

Original issue reported on code.google.com by rahul.ak...@gmail.com on 12 Jun 2009 at 3:13

[GoogleCodeExporter]

Original comment by rahul.ak...@gmail.com on 12 Jun 2009 at 3:51

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

As MarkB reminds on IRC, this issue relates to behavior in XHTML mode, 
which is how we have the W3C test suite checked into SVN. This may not be 
an issue in HTML mode (vague since I'm adding this comment as a bulk edit 
across multiple issues). The manual results files actually reflect HTML 
mode behavior.

Original comment by rahul.ak...@gmail.com on 12 Jun 2009 at 4:21

[GoogleCodeExporter]

The xf:input field is disabled due to the ref being missing. I'm assuming this 
is not
a defect but is a design choice since the XForms spec seem to indicate that the
ref="tag" should be present in section 8.1.2. Any one else have any comments? I 
think
the tests need to be updated since the input should not be visible unless bound 
to a
particular data model. In this case it is an issue with the WC3 tests.

Original comment by erik...@gmail.com on 18 Sep 2009 at 8:58

[GoogleCodeExporter]

WC3 Has been notified. I will update this issue once I get a response.

Original comment by erik...@gmail.com on 23 Sep 2009 at 3:42

• Changed state: OnHold

[GoogleCodeExporter]

The W3C changed these tests, they have been pulled into our test suite, and the 
automated tests all pass now.

Original comment by John.Boyer.PhD@gmail.com on 11 Feb 2010 at 7:15

• Changed state: Fixed