Console Filtering: should User messages only be persistent?

[Zac Spitzer]

The new option for console filtering "User messages only" (i.e hide browser generated [violation] warnings) 

isn't sticky and needs to be checked every single time dev tools is opened.

Could this be made a persistent option under settings?

Also, "User messages only" is rather obscure, who is the user? "Hide browser violations and warnings" would be better

https://bugs.chromium.org/p/chromium/issues/detail?id=717776

[Kayce Basques]

If you're going to the trouble of opening up Settings to change something, I think most times you want that thing to be persistent.

My opinion is that most things should be persistent, but the DevTools UI should warn you when you've configured something to a value other than the default. This is how it handles "Disable Cache" in the Network panel (it shows a warning icon next to the "Network" tab).

Somebody recently requested for "Enable Request Blocking" to persist, too

[Deep Bass]

Indeed. This is rather annoying to say the least.

On Thursday, June 15, 2017 at 5:37:34 AM UTC+2, Zac Spitzer wrote:

The new option for console filtering "User messages only" (i.e hide browser generated [violation] warnings) 

isn't sticky and needs to be checked every single time dev tools is opened.

Could this be made a persistent option under settings?

https://bugs.chromium.org/p/chromium/issues/detail?id=717776