338697 - Errors disappear from my JSConsole with javascript.options.strict to true

Status: RESOLVED INVALID

(Core Graveyard :: Error Console, defect)

Description

[Ria Klaassen (not reading all bugmail)]

Steps to reproduce:
1. Set the prefs javascript.options.showInConsole and javascript.options.strict both to true.
2. Start your browser and call the JSConsole. You'll see at least one error about safebrowsing (that's not what this bug is about) or else go to http://www.compuserve.nl/nieuws/categorie.aspx?cat=Nieuwsthema to get one.
3. Then go to http://www.nu.nl/
4. Suddenly the errors will disappear from the console. There are more sites with a cleaning effect but not as consistent as www.nu.nl.

Expected behaviour: that errors should stay in the console until the end of the session.

Comment 1

[Ria Klaassen (not reading all bugmail)]

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

Comment 2

[:Gavin Sharp [email: [e-mail]]]

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.

Comment 3

[Ria Klaassen (not reading all bugmail)]

That makes sense, but should it also erase the errors?
You hardly have the chance to see them.

Comment 4

[:Gavin Sharp [email: [e-mail]]]

Only 250 can appear at a time, so once 250 are displayed, the oldest ones are removed as new ones are added. I believe the reason for that limit was that things got really slow with more items than that. That was in 2001, though, so maybe the limit can be increased now.

Can you confirm that the 250 item limit is being hit? If so, I think this bug can be moved to Core: JavaScript Console and be re-summarized "consider increasing limit for items in the console", or something like that.

Comment 5

[:Gavin Sharp [email: [e-mail]]]

Oh, I think I see what you mean. Instead of 250 items total, maybe it could be changed to 100 items per category?

Comment 6

[Ria Klaassen (not reading all bugmail)]

Can't be much more or less than 250 items indeed.
I think 50 items for errors is enough for a whole session (I hope so).
The warnings and messages can stay the same.
I don't know how many people use that javascript.options.strict setting.
I didn't set it deliberately, but an extension (I think web developer extension) must have changed this.
Personally I think that all errors should stay until the end of the session.
Glad that the riddle is solved in any case.

Comment 7

[Ria Klaassen (not reading all bugmail)]

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.