Closed Bug 610619 Opened 11 years ago Closed 9 years ago

browser_contentAreaClick.js | Test timed out (must wait for focus)

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: dao, Unassigned)

References

Details

(Keywords: intermittent-failure)

Attachments

(2 files)

hm, the screenshot is interesting, looks like hanged and there is something like a small dialog in the top right part of the window (not visible but something like a repaint issue).
Attached image screenshot
Hm, I guess when these screenshots are taken, there should be another open window...
Rev3 Fedora 12x64 mozilla-central opt test mochitest-other on 2010/12/22 20:02:04
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1293076924.1293077954.27510.gz
Clearly some kind of focus related issue here. I couldn't reproduce it myself but one thing I could guess is that immediately after the browser.xul DOM is loaded its content window might not be properly in place. This patch might help but I can't see it hurting.

It waits till the delayedStartup has run for the new browser.xul, then makes sure the main browser window is focused and then finally focuses the content area and continues. It passes on try.
Attachment #516633 - Flags: review?(mak77)
Comment on attachment 516633 [details] [diff] [review]
wait for window to open before focusing content

I agree that it's worth a shot and cleaner than a bunch of executeSoon
Attachment #516633 - Flags: review?(mak77) → review+
Landed: http://hg.mozilla.org/mozilla-central/rev/bf2db29072f4

Not going to call this fixed just yet, let's see how it does.
comment 104 was mi-starred
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.