Closed
Bug 356572
Opened 19 years ago
Closed 10 years ago
Error Console Icon Should Be Different to that of Browser Window
Categories
(Toolkit Graveyard :: Error Console, enhancement)
Toolkit Graveyard
Error Console
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: reply, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7
Each time I make a change to my application, I have to close the main browser window and re-start the Firefox process. As I test my web applications, I find myself accidentally closing the error console window because I think it's the main browser window. This is because they have exactly the same icon. This costs me additional clicks, which I'm sure you can appreciate adds up.
Reproducible: Always
Comment 1•19 years ago
|
||
Could not find a similar request, so -> New.
It is not difficult however to give the window its own icon. Place it under the name jsconsoleWindow.ico in the folder C:\Program Files\Mozilla Firefox\chrome\icons\default
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•19 years ago
|
URL: *** any ***
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → Trunk
| Assignee | ||
Updated•18 years ago
|
Product: Firefox → Toolkit
Comment 2•10 years ago
|
||
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.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Comment 3•10 years ago
|
||
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.)
Status: RESOLVED → REOPENED
Component: Error Console → Developer Tools: Console
Product: Toolkit → Firefox
Resolution: WONTFIX → ---
Comment 4•10 years ago
|
||
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.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Component: Developer Tools: Console → Error Console
Product: Firefox → Toolkit
Resolution: --- → WONTFIX
| Assignee | ||
Updated•10 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•