975936 - JS warnings may cause error to disappear

Status: RESOLVED INVALID

(DevTools :: Console, defect, P3)

Description

[Luke]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:28.0) Gecko/20100101 Firefox/28.0 (Beta/Release)
Build ID: 20140212005842

Steps to reproduce:

Went to a page that causes a JS error, and a ton of JS warnings.


Actual results:

Under "JS", you can check Error, but not Warnings, but even still, apparently it rotates the logs, and with over 200 warnings, the error disappears.


Expected results:

Error should not be removed due to warnings.

Comment 1

[Liz Henry (:lizzard) (relman/hg->git project)]

Hi Luke, can you give us an example url? Thanks!

Comment 2

[Mihai Sucan [:msucan]]

Thanks for the bug report.

This is working as expected, but it is weird behavior indeed. Logs are rotated based on category, not severity. So JS warnings are counted together with errors.

Comment 3

[Luke]

Yeah, from what I understand it's in separate queues for Net, exception, logging, css (hence the separate log limit options) but it can blank out errors with warnings even when you only have warnings checked. What if errors and warnings, etc. were their own separate queues? Also 200 by default seems a bit small, is it for performance considerations?

Comment 4

[Panos Astithas (he/him) [:past] (please ni?)]

I've never come across a web app that produced hundreds of JS warnings. Do you happen to use some particularly bug-ridden library?

Comment 5

[Nicolas Chevobbe [:nchevobbe]]

I think this was related to the old console filters (category + level)
As we don't have this anymore, and as the STR isn't clear, I'm closing this bug.