608953 - [SeaMonkey] mochitest-browser-chrome: .../browser/browser_bug562890.js reports 2 unexpected 'Console message'

Status: NEW

(SeaMonkey :: Testing Infrastructure, defect)

Description

[Serge Gautherie (:sgautherie)]

Bug 604136 comment 9:
{
Serge Gautherie (:sgautherie)      2010-10-31 03:10:39 PDT

TEST-INFO |
chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_bug562890.js
| Console message: [JavaScript Warning: "assignment to undeclared variable
gThemes" {file: "chrome://navigator/content/navigator.js" line: 83}]
TEST-INFO |
chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_bug562890.js
| Console message: [JavaScript Error: "aCallback is not a function" {file:
"chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/head.js"
line: 254}]
}

Bug 604136 comment 10:
{
The first message is rather unexpected:
http://mxr.mozilla.org/comm-central/search?string=gThemes&case=1&find=%2Fsuite%2Fbrowser%2Fnavigator%5C.js%24

I wonder about the second message.
}

The "browser-window" run does not report these messages.
Firefox is fine.

This is not causing test failure so 'minor' ftb.

Comment 1

[[e-mail]]

(In reply to comment #0)
> JavaScript Warning: "assignment to undeclared variable
> gThemes" {file: "chrome://navigator/content/navigator.js" line: 83}
As you point out, gThemes is declared on line 70...

> JavaScript Error: "aCallback is not a function" {file:
> "chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/head.js"
> line: 254}
We need to work out where this code is and who calls it.