Closed
Bug 80702
Opened 23 years ago
Closed 8 years ago
More advanced sorting features in Error Console
Categories
(Toolkit Graveyard :: Error Console, enhancement)
Toolkit Graveyard
Error Console
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bugzilla, Unassigned)
References
Details
It could be nice if you could sort by: - Type - Text - Source File - Line number
Yeah, would be nice. ;-) Marking p4, enhancement, and future.
Severity: normal → enhancement
Priority: -- → P4
Target Milestone: --- → Future
Reporter | ||
Comment 2•23 years ago
|
||
javascript console...
Assignee: pchen → hewitt
Component: XP Apps → JavaScript Console
QA Contact: sairuh → jrgm
Updated•23 years ago
|
Status: NEW → ASSIGNED
Comment 3•23 years ago
|
||
Here, have a vote. :) This would be very useful to me.
Summary: More advanced sorting features in JavaScript console → More advanced sorting features in Error Console
Assignee | ||
Updated•16 years ago
|
Product: Core → SeaMonkey
Updated•16 years ago
|
Assignee: hewitt → nobody
Status: ASSIGNED → NEW
Priority: P4 → --
QA Contact: jrgmorrison → error-console
Target Milestone: Future → ---
Comment 4•15 years ago
|
||
I'm not sure what the purpose of all these sort functions would be, by type can just as easily be accomplished by moving to the type's tab, by text might be nice, source file doesn't really make sense as the errors generally come in sorted by source file, and by line number, how is that useful?
Updated•15 years ago
|
Updated•14 years ago
|
Product: SeaMonkey → Toolkit
QA Contact: error-console → error.console
Comment 5•8 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: 8 years ago
Resolution: --- → WONTFIX
Comment 6•8 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 7•8 years ago
|
||
Doesn't translate to browser console, so resolving
Status: REOPENED → RESOLVED
Closed: 8 years ago → 8 years ago
Component: Developer Tools: Console → Error Console
Product: Firefox → Toolkit
Resolution: --- → WONTFIX
Assignee | ||
Updated•8 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•