First, please be aware that what you label as bad is really cool for other people, and that the team is making choices to improve the tools for the majority of our user.
Filtering in web console is confusing. In pre FF57 DevTools filtering was clear and obvius.
It was simply not. The UI was complex and confused people.
There was Network: CSS, JS, Security, Log, Server filters.
Now there are: Erorrs, Warnings, Logs, Informations, Debuging Logs.
Now there are Errors Warnings Logs Info Debug | CSS XHR Requests.
You can see that “actual” logs (consoleAPI calls) are ordered by “level” (console.error , .warn, .log, .info, .debug) and other, less-used type of messages are differentiated.
There are 2 things missing, “Security” and “Server”. Server logs are no longer supported natively since there are no parts of the ConsoleAPI specification and there is a webextension to make them available.
“Security” is being discussed in https://bugzilla.mozilla.org/show_bug.cgi?id=1410369.
What the heck are Infromations about (maybe about flight to the moon)? Which erreors are shown when Erorrs filter are on (maybe about Chernobyl Recator)?
- Mind your language, 2. This show all the Errors (JS Exception, Evaluation Results exception, bad use of console input helpers, …). I guess you were used to the old console frontend where you could apply fine-grained level to every sorts of messages, but overall, this is confusing. If you want to see errors, you probably want to see all the different “types”.
We can always discuss if you think this does not work well and provide good examples showing why this is a blocker for you, and find solution (and consensus) for everyone.
And why you hide those filters? Why you removed color indicators in those filters?
Because as you noticed, Firefox and the devtools were being redesigned to look nicer and cleaner. The text label and the placement on the filter are quite explicit which made us think these color could go away. Again, if you give us some examples showing why this is an issue for you, we can discuss it and find solution.
It is even well not visible which filters are on and which are off.
I am confused, the filters do have an active and an inactive state, so you can clearly see which are enabled or not. We follow the same pattern than in all the other tools. If you say that you don’t see them because the filter bar is hidden, well, 1. you can open it, and as long as you don’t close it, it will always be opened when you open the console, 2. If there are “default” logs (error, warn, log, info, debug) hidden, we display an “X items hidden by filters” which can alert you you might miss something.
Why? Why? Why? Why? Why!?! Because Google Chrome made this way? If yes, this is pathetic argument.
It does not look the same at all to me.
Please note that it is actively being worked on as we try to find the right balance between cleanness and usability (See https://twitter.com/violasong/status/926189788486557697). You might want to follow https://twitter.com/FirefoxDevTools where we ask people for feedback or come and chat in our Slack
(And those colors in dark theme, Jesus Holy Mary and other saints, why is there so much contrast! between dark an lighter areas!?)
Can you tell us what you are calling dark areas ? Those color were carefully chosen to be accessible so everyone, including people with visual impairments can differentiate them. If you have specific suggestion, tell them and we can discuss it.
Overall, remember that we are people, trying to provide the best tool for our users. You can always come and give us feedback and we’ll be happy to discuss and make changes if we find they are legit.