547688 - [HTML5] toolkit/content/tests/widgets/test_radio.xul fails

Status: RESOLVED WORKSFORME

(Core :: DOM: HTML Parser, defect, P1)

Description

[Henri Sivonen (:hsivonen)]

150311 ERROR TEST-UNEXPECTED-FAIL | /tests/toolkit/content/tests/widgets/test_radio.xul | accesskey focuses radiogroup - got [object XULElement], expected [object XULElement]
150312 ERROR TEST-UNEXPECTED-FAIL | /tests/toolkit/content/tests/widgets/test_radio.xul | accesskey selects radio - got [object XULElement], expected [object XULElement]
150314 ERROR TEST-UNEXPECTED-FAIL | /tests/toolkit/content/tests/widgets/test_radio.xul | accesskey on disabled radio doesn't change selection - got [object XULElement], expected [object XULElement]

Comment 1

[Henri Sivonen (:hsivonen)]

I don't see any connection to the HTML5 parser here.

Comment 2

[Henri Sivonen (:hsivonen)]

This could be random and cross-platform.

Comment 3

[Henri Sivonen (:hsivonen)]

WFM on Mac and Linux x86_64.

Comment 4

[Henri Sivonen (:hsivonen)]

Fails on Windows tryserver still.

Comment 5

[Henri Sivonen (:hsivonen)]

This test case fails with html5.enable=true on Windows tryserver. The failure messages aren't helpful (got [object XULElement], expected [object XULElement]). I don't see any connection to the HTML parser.

Do you have ideas on how this could depend on the HTML parser?

Comment 6

[Neil Deakin]

Does setting html5.enable=true cause different tests to run beforehand?

Comment 7

[Henri Sivonen (:hsivonen)]

The set of tests is the same, but the following tests have some pref-sensitivity:
/content/base/test/test_bug527896.html
/content/base/test/test_bug503473.html
/parser/htmlparser/tests/mochitest/test_bug502091.html
/parser/htmlparser/tests/mochitest/test_compatmode.html

Comment 8

[Henri Sivonen (:hsivonen)]

For the test run, I had disabled these tests:
http://mxr.mozilla.org/mozilla-central/source/dom/tests/mochitest/ajax/offline/test_foreign.html?force=1
http://mxr.mozilla.org/mozilla-central/source/dom/tests/mochitest/ajax/offline/test_updatingManifest.html?force=1
http://mxr.mozilla.org/mozilla-central/source/parser/htmlparser/tests/mochitest/test_html5_tree_construction.html?force=
http://mxr.mozilla.org/mozilla-central/source/toolkit/components/startup/tests/browser/browser_bug537449.js
http://mxr.mozilla.org/mozilla-central/source/toolkit/components/startup/tests/browser/browser_bug511456.js

Comment 9

[Henri Sivonen (:hsivonen)]

It seems that this failure was caused by bug 546648 and was fixed by the patch for that bug.