[SeaMonkey 2.1] mochitest-browser-chrome: "browser_focus_steal_from_chrome.js | Timed out"

RESOLVED FIXED

Status

()

--
major
RESOLVED FIXED
9 years ago
8 years ago

People

(Reporter: sgautherie, Assigned: iann_bugzilla)

Tracking

(Blocks: 1 bug)

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(blocking2.0 -)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

9 years ago
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.3a1pre) Gecko/20091218 SeaMonkey/2.1a1pre] (home, optim default) (W2Ksp4)
(Reporter)

Comment 1

9 years ago
{
Console message: [JavaScript Error: "BrowserSearch is not defined" {file: "chrome://mochikit/content/browser/dom/tests/browser/browser_focus_steal_from_chrome.js" line: 133}]

Console message: [JavaScript Error: "BrowserSearch is not defined" {file: "chrome://mochikit/content/browser/dom/tests/browser/browser_focus_steal_from_chrome.js" line: 149}]

Timed out
}
Summary: [SeaMonkey 2.1] mochitest-browser-chrome: 2 "Console message: [JavaScript Error: "BrowserSearch is not defined" {file: "chrome://mochikit/content/browser/dom/tests/browser/browser_focus_steal_from_chrome.js" line: 1xx}]" → [SeaMonkey 2.1] mochitest-browser-chrome: "browser_focus_steal_from_chrome.js | Timed out"

Comment 2

9 years ago
SeaMonkey does not have a search bar.
See Also: → bug 534420
Why are the "browser" tests shared between different products??

Comment 4

9 years ago
I think these are actually DOM tests that just happen to use the browser for test purposes.

SeaMonkey specific browser tests are in [comm-central]/suite/browser/tests/
Firefox specific browser tests are in [mozilla-central]/browser/*/tests/
That's correct.  Things that are in dom/ are supposed to be testing universal DOM functionality.
And a "steal focus from chrome" test does sound like it should live in dom/

Comment 7

9 years ago
Then it would be good if the test would be done with some element that is at visible in both browsers running those tests or it should fail gracefully (possibly with a TODO) when the element to test with isn't found in the first place.
(Reporter)

Comment 8

9 years ago
Linux and MacOSX too:
{
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1266802111.1266803198.17758.gz
Linux comm-central-trunk debug test mochitest-other on 2010/02/21 17:28:31

http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1266802005.1266803746.19182.gz
OS X 10.5 comm-central-trunk debug test xpcshell on 2010/02/21 17:26:45
}
Severity: normal → major
OS: Windows 2000 → All
Hardware: x86 → All
(Reporter)

Comment 9

9 years ago
Bug still there.
Masayuki, what's the plan to solve this?
Blocks: 125282
blocking2.0: --- → ?
No longer depends on: 125282
(Reporter)

Comment 10

9 years ago
And this failure is causing at least the 4 next browser_Browser.js failures (because a tab is left open).
No longer blocks: 470184
Component: Layout: Form Controls → DOM
QA Contact: layout.form-controls → general
Not blocking the release on this.
blocking2.0: ? → -
(Assignee)

Comment 12

8 years ago
Created attachment 472196 [details] [diff] [review]
Switch to a more generic chrome element patch v0.1 [Checked in: comment 14]

Switches to finding an element with an id urlbar making the test not dependent on code sitting in /browser (i.e. BrowserSearch).
Is test only but asking for a= anyway.
Assignee: nobody → iann_bugzilla
Status: NEW → ASSIGNED
Attachment #472196 - Flags: review?(bzbarsky)
Attachment #472196 - Flags: approval2.0?
Attachment #472196 - Flags: review?(bzbarsky) → review+
(Assignee)

Comment 13

8 years ago
Comment on attachment 472196 [details] [diff] [review]
Switch to a more generic chrome element patch v0.1 [Checked in: comment 14]

As a test a=testing NPODB
Attachment #472196 - Flags: approval2.0?
(Assignee)

Comment 14

8 years ago
Comment on attachment 472196 [details] [diff] [review]
Switch to a more generic chrome element patch v0.1 [Checked in: comment 14]

http://hg.mozilla.org/mozilla-central/rev/fe3a1059a92b
Attachment #472196 - Attachment description: Switch to a more generic chrome element patch v0.1 → Switch to a more generic chrome element patch v0.1 [Checked in: comment 14]

Updated

8 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.