984337 - To keep the Web Console less noisy, do not enable CSS Warnings, CSS Log and JS Warnings when clicking the CSS and JS categories rescpectively

Status: RESOLVED WONTFIX

(DevTools :: Console, enhancement)

Description

[Kostas]

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0 (Beta/Release)
Build ID: 20140212131424

Steps to reproduce:

Based on the work that is been doing for the bug https://bugzilla.mozilla.org/show_bug.cgi?id=909803
currently in Nightly 30, using a clean profile,
in Web Console, in the CSS and JS toolbar buttons,
(I don't mention the Net tab because it's planned to be removed https://bugzilla.mozilla.org/show_bug.cgi?id=909754)
only the first filters, named both "Errors" are enabled:
CSS:  Errors/-/-
JS: Errors/-

Click these buttons to disable them.
Then click them again to re-enable them.


Actual results:

ALL the filters are enabled:
CSS:  Errors/Warnings/Log and 
JS: Errors/Warnings


Expected results:

I suggest, when re-enabling the toolbar buttons
only the enabled-by-default filters to be enabled:
CSS:  Errors/-/-
JS: Errors/-

Comment 1

[Paul Silaghi, QA [:pauly]]

I think the purpose of this is to speed up the things by enabling all the options with one click. If you want just one option, you can click just on it.

Comment 2

[Kostas]

With my suggestion, I believe that the Web Console is ensured to be is less noisy, 
not only in a clean profile ("by default"), but in everyday use as well,
no matter which combination of the toolbar buttons you choose to disable/re-enable.

If the user wants more filters or even all,
then yes, he can manually enable more filters, as he wishes.

Comment 3

[Kostas]

With bug 971798, the CSS Log category (now renamed Reflows) is no longer enabled when clicking the CSS category in FF31.

Comment 4

[Mihai Sucan [:msucan]]

Thanks for the suggestion. If we make the suggested change we will break user expectations for how the toggling of filters works with those toolbar buttons. I doubt users are having issues with how the buttons work now.

I'm going to mark this bug as wontfix, for now.