content/html/content/test/forms/test_input_color_picker_popup.html and content/html/content/test/forms/test_input_color_picker_update.html both timeout on the mozilla-b2g26_v1_2 branch, note they do not timeout on trunk.

In case it wasn't clear from the title, this the b2g desktop build: https://tbpl.mozilla.org/php/getParsedLog.php?id=30326825&tree=Mozilla-B2g26-v1.2

Disabled the tests: https://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/f4b76424463e

CCing some people have been working on the color picker stuff lately in case they want this test running on b2g26.

(This is the first I've seen these tests, FWIW. Looks like they were added in bug 885996.) It looks like these tests expect that we spawn a dialog when the colorpicker is clicked (which is self-evident from the test name for the "popup" one -- and the other one ("update") has "synthesizeMouseAtCenter(element, {});" which seems to be trying to trigger a dialog) We don't have a colorpicker dialog implemented yet for B2G, IIUC (bug 875751). So it makes sense that these tests would have issues there, & disabling these tests on B2G seems correct.

(In reply to Andrew Halberstadt [:ahal] from comment #0) > content/html/content/test/forms/test_input_color_picker_popup.html and > content/html/content/test/forms/test_input_color_picker_update.html both > timeout on the mozilla-b2g26_v1_2 branch, note they do not timeout on trunk. Oh, that part is interesting. Not sure offhand what would be causing that difference, but in any case, the <input type="color"> pref wasn't ready to be turned on by default anywhere until Firefox 28 (bug 930277), and even now isn't ready to be turned on by default on B2G. So, disabling some <input type="color"> tests on a 26-based branch is definitely fine.

Thanks!