Could also be a DOM Level 0 bug I think, reading the description of that component. It is weird that a website has the power to delete things. Here I described the same problem when I saw it for the first time but it had nothing to do with the bug where I reported it: https://bugzilla.mozilla.org/show_bug.cgi?id=338541#c20
Assignee: js-console → general
QA Contact: jrgmorrison → ian
There is a limit of 250 total items (warnings+messages+errors) displayed in the JS Console at one time. It seems to me that those sites just generate a lot of warnings and therefore flush the old ones off the list.
That makes sense, but should it also erase the errors? You hardly have the chance to see them.
OS: Windows XP → All
Hardware: PC → All
Oh, I think I see what you mean. Instead of 250 items total, maybe it could be changed to 100 items per category?
Assignee: general → js-console
QA Contact: ian → jrgmorrison
Resolving invalid because this bug as filed does not exist. It is simply a function that I misunderstood. I considered turning it into a RFE as suggested by Gavin, but I think the problem is handled reasonable well in the Console2 extension, where you can hide doubles and blacklist domains. I considered also that, if it were a problem for other people, this bug had been filed already. Also serious performance problems on trunk builds (sometimes when you call the JSConsole the entire application becomes unresponsive) played a role not to turn this bug into a RFE.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → INVALID
Component: Error Console → Error Console
Product: SeaMonkey → Core Graveyard
You need to log in before you can comment on or make changes to this bug.