Closed
Bug 147015
Opened 22 years ago
Closed 14 years ago
JS Console should group same errors
Categories
(Toolkit Graveyard :: Error Console, enhancement)
Toolkit Graveyard
Error Console
Tracking
(Not tracked)
People
(Reporter: mark.slater, Unassigned)
References
(Depends on 1 open bug)
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0+) Gecko/20020524 BuildID: 2002052408 It would be nice if the JS Console would group javascript errors that are exactly the same, eg. if some site's JS has 1'000 instances of the same occurring error, the JS console shouldn't fill itself with 1'000 errors, but group it under 1 error message with a twisty to show all 1'000 instances of the error.
Comment 1•22 years ago
|
||
I don't think this would be a good default behavior, since the significance of a much repeated error might depend upon the errors imediatly before and after it. However, a checkbox in the JS console to turn this on would be a good idea. Confirming as NEW, changing Platform/OS to "All/All".
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 98 → All
Hardware: PC → All
Comment 2•20 years ago
|
||
Perhaps the right thing to do here is exponential backoff (possibly in the console service itself)? That is keep track of errors we've seen. If we get one just like one we already got, and we've gotten it a lot recently (the exact definitions of "a lot" and "recently" are up for debate") we ignore it. This way as long as an error is repeating we will report it, but say no more often than once a second (or whatever "recently" is), though in the first second of reporting, for example, it we would report it as many times as it happens. Thoughts? We really do want something like this on by default if we're going to turn on CSS error reporting in release builds....
Comment 3•20 years ago
|
||
*** Bug 206874 has been marked as a duplicate of this bug. ***
Comment 4•19 years ago
|
||
Rather than setting some values for "a lot" and recently I'd say that an error isn't displayed if it matches the previous one. If it doesn't, a new one is created, otherwise just increase a counter. eg: CSS Error 1 CSS Error 2 [5] JS Error 1 JS Error 2 [19] JS Error 1 If you mean by "ignore an error" do not display it, then I can't agree. At least there needs to be a visible change, or some info that this error just occured again. Imagine you got a link list where's a Javascript onmouseover error. It maybe would report the first 10 entries, or however many get triggered "recently" and then it would stop - could be confusing. Moreover blocking/ignoring the errors after 10 repetitions or after there were "a lot" "recently" only reduces the error spam instead of completely removing it. Imagine the error occurs all "recently"+1 times, having it displayed all the time though no new information is displayed.
Comment 5•19 years ago
|
||
Is this bug a dublicate of bug 80704 - both are about removing dublicate entries in JS console
Assignee | ||
Updated•16 years ago
|
Product: Core → SeaMonkey
Updated•16 years ago
|
Assignee: hewitt → nobody
QA Contact: jrgmorrison → error-console
Updated•15 years ago
|
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Product: SeaMonkey → Toolkit
QA Contact: error-console → error.console
Resolution: --- → DUPLICATE
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
•