1064242 - Browser console without open browser windows can't open view source windows for files triggering errors/warnings

Status: NEW

(DevTools :: Console, defect, P3)

Description

[:Gijs (he/him)]

STR:

0. Do something which triggers an error which appears in the browser console, with a link to the file causing the error/warning
1. Close your open browser windows (if you're not on OS X, open the browser console from the last window)
2. Click the file link for an error/warning

ER:
Opens view source window for the file + line number

AR:
View source window doesn't open. If you're on OS X and open the browser console after the last browser window has closed, you get "this.gViewSourceUtils is undefined". If you opened the console from a browser window and closed the window, gViewSourceUtils itself breaks down somewhere...

Comment 1

[Tom Peeters]

This bug also occurs when trying to run a xulrunner application using the firefox binary (by using the -application switch). You are able to open the browser console by using the -jsconsole argument, but clicking on actual error messages will result in the same error.

It seems that the browser console depends on certain elements inside the main browser window. I was not able to find out how to re-create those in my XUL app and therefor, the browser console is not feature complete replacement for the error console (yet).

Given the current state of the xulrunner project, it would be great if this issue could be addressed.

Comment 3

[Nicolas Chevobbe [:nchevobbe]]

Still relevant.
We now have an error in the Browser Console:

TypeError: window.top is null viewSourceUtils.js:76:5

Comment 4

[Meron Watts]

Attachment: same problem

Thanks from icmongusand1972.