Jonathan Griffin (:jgriffin) Reporter
	Description • 12 years ago

On B2G, several DOM tests timeout, and cause the test chunk they're running in to get aborted due to too many timeouts.  These will be disabled for future B2G test runs.

full log:  http://brasstacks.mozilla.com/autologserver/showlog?file=d6bd879c-f834-11e1-a9d1-22000af4836f.txt.gz

affected tests:
/tests/dom/tests/mochitest/general/test_497898.html
/tests/dom/tests/mochitest/general/test_bug628069_1.html

I'll add additional tests to this bug as I identify them.

	Jonathan Griffin (:jgriffin) Reporter
	Comment 1 • 12 years ago

Also affected:

/tests/dom/tests/mochitest/whatwg/test_bug500328.html
/tests/dom/workers/test/test_suspend.html

	Boris Zbarsky [:bzbarsky]
	Comment 2 • 12 years ago

Do we know why that first test times out?  Is it window.open that's broken, or focus stuff?

	Jonathan Griffin (:jgriffin) Reporter
	Comment 3 • 12 years ago

(In reply to Boris Zbarsky (:bz) from comment #2)
> Do we know why that first test times out?  Is it window.open that's broken,
> or focus stuff?

Focus stuff may be broken, see bug 788866.  I'm not sure whether window.open is working these days on B2G or not.

	Mounir Lamouri (:mounir)
	Comment 4 • 12 years ago

Jonathan, maybe you should open a bug about focus not working if you can narrow down what is actually broken (which seems something you did according to a comment you wrote in another bug).

	Jonathan Griffin (:jgriffin) Reporter
	Comment 5 • 12 years ago

(In reply to Mounir Lamouri (:mounir) from comment #4)
> Jonathan, maybe you should open a bug about focus not working if you can
> narrow down what is actually broken (which seems something you did according
> to a comment you wrote in another bug).

I filed bug 788866 about document.hasFocus() always being false, even after calls to window.focus() and iframe.focus().  Do I need to narrow it down further?