Closed
Bug 535903
Opened 15 years ago
Closed 15 years ago
[SeaMonkey 2.1] mochitest-browser-chrome: "browser_focus_steal_from_chrome.js | Timed out"
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
blocking2.0 | --- | - |
People
(Reporter: sgautherie, Assigned: iannbugzilla)
References
(Blocks 1 open bug, )
Details
Attachments
(1 file)
598 bytes,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
[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•15 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 3•15 years ago
|
||
Why are the "browser" tests shared between different products??
![]() |
||
Comment 4•15 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/
![]() |
||
Comment 5•15 years ago
|
||
That's correct. Things that are in dom/ are supposed to be testing universal DOM functionality.
![]() |
||
Comment 6•15 years ago
|
||
And a "steal focus from chrome" test does sound like it should live in dom/
![]() |
||
Comment 7•15 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•15 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•15 years ago
|
||
Bug still there.
Masayuki, what's the plan to solve this?
Reporter | ||
Updated•15 years ago
|
Reporter | ||
Comment 10•15 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: CcMcBuildIssues
Component: Layout: Form Controls → DOM
QA Contact: layout.form-controls → general
Assignee | ||
Comment 12•15 years ago
|
||
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?
![]() |
||
Updated•15 years ago
|
Attachment #472196 -
Flags: review?(bzbarsky) → review+
Assignee | ||
Comment 13•15 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•15 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•15 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•