From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0+) Gecko/20020524
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
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".
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.
We really do want something like this on by default if we're going to turn on
CSS error reporting in release builds....
*** Bug 206874 has been marked as a duplicate of this bug. ***
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.
CSS Error 1
CSS Error 2
 JS Error 1
JS Error 2
 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
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.
Is this bug a dublicate of bug 80704 - both are about removing dublicate
entries in JS console
*** This bug has been marked as a duplicate of bug 80704 ***