386138 - Error Console should display information about a tab it's associated with

Status: RESOLVED WONTFIX

(Toolkit Graveyard :: Error Console, enhancement)

Description

[Roman R.]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4

I just noticed that Error Console is producing error messages (they are being added to the list at the rate of slightly faster that once per second). I can see the error, script name, and can see the whole script, but I don't know which tab (site) started the script so that I could get more information that would allow FF developers to fix the bug. See, I've gone through all open tabs, and none of them has launched the script. I believe it was launched by one of sites a tab with which I've closed.

Reproducible: Didn't try

Steps to Reproduce:
1.
2.
3.

Comment 2

[Roman R.]

Jesse, I disagree with you because if bug 386139 doesn't get fixed, there will be no way to tell if a script that should've been terminated is still running if Error Console is made to only show errors for selected tab.

Comment 3

[Matthew Cline]

I think what's desired here is for an error message to include the URL of the top-level document in which it happened.  Confirming, as it seems useful.

Comment 4

[Roman R.]

Yes, that's what is desire here, Matt.

Comment 5

[Kevin Dangoor]

It seems like this is fixed with the addition of the Web Console in Firefox 4, which is specifically set up to display errors for a given tab.

Comment 7

[Brian Grinstead [:bgrins]]

The Error Console has been removed in favor of the Browser Console (see Bug 1278368), and the component is going to be removed.  If this bug is also relevant in the Browser Console, please reopen and move this into Firefox -> Developer Tools: Console.

Comment 8

[Zack Weinberg (:zwol)]

I am mass-reopening and re-componenting every single one of the Toolkit:Error Console bugs that appear to have been closed without anyone even *glancing* at whether they were relevant to the Browser Console.

If you want to close a whole bunch of old bugs -- FOR ANY REASON -- it is YOUR RESPONSIBILITY to check EVERY SINGLE ONE OF THEM and make sure they are no longer valid.  Do not push that work onto the bug reporters.

(It's okay to close bugs that haven't been touched in years when they don't have enough information for you to figure out whether the problem is still relevant to the current software - the reporter probably isn't coming back to clarify.  But that is the ONLY situation where it is okay.)

(I'm going to have to do this in two steps because of the way the "change several bugs at once" form works.  Apologies for the extra bugspam.)

Comment 9

[Brian Grinstead [:bgrins]]

The Error Console feature was removed entirely from the tree in Bug 1278368 and the bugzilla component is now being removed. We’ve migrated bugs that seem to also affect the Browser Console into the devtools component, please move this over if it was missed.