W3C testsuite Chater 10 failing tests - FF3 (regression from manually maintained test results)

[GoogleCodeExporter]

Specifically:

10.3.d, 10.3.e, 10.3.f(not regression - see below) - appears to be failing
because of a bug in the repeat content rewire and/or refresh processing.
10.4.f likely fails due to a faulty processing of the repeat index,
especially when index() used in binds.
10.5.a - Last redundant step in Selenium script causes the failure.

TBC...

Note:
10.3.f, 10.8.f, 10.17.c, 10.17.d are NOT a regression failures.

Also note that we have a 'progression' (as oppose to regression :)
10.15.a, 10.18.e do not fail anymore.

Original issue reported on code.google.com by moishe.t@gmail.com on 30 May 2009 at 12:50

[GoogleCodeExporter]

10.7.a, 10.7.1.a and 10.7.1.b seem to work fine - this looks like Selenium 
script
problem. Noted that FF3 places cursor AFTER the 'text contents' of the input 
control,
while IE7b places it before. This is not a violation of the spec I believe.

10.8.1.a and 10.8.1.b seem genuinely failing to dispatch the event.

10.14.a, 10.14.b, 10.14.1.a, 10.14.1.b, are reported as "Selenium failure..."

Finally, 10.15.a is failing likely either due to the timing issue with the 
Selenium
script or the not truly 'modal' nature of the xforms:message.

Original comment by moishe.t@gmail.com on 4 Jun 2009 at 4:18

[GoogleCodeExporter]

Original comment by moishe.t@gmail.com on 4 Jun 2009 at 5:04

[GoogleCodeExporter]

Original comment by moishe.t@gmail.com on 5 Jun 2009 at 3:52

• Added labels: Component-Tests

[GoogleCodeExporter]

Update: as of 31-08-2009 there are 16 tests still failing in FF3:
10.3.f
10.4.f
10.5.a
10.7.a
10.7.1.a
10.7.1.b
10.8.f
10.8.1.a
10.8.1.b
10.14.a
10.14.b
10.14.1.a
10.14.1.b
10.15.a
10.17.c
10.17.d

Original comment by moishe.t@gmail.com on 31 Aug 2009 at 6:50