Make "Selected Context Only" persist in Chrome DevTools console settings

Question

I get a ton of misc errors from misc Chrome Extensions in my console. If I go to settings and check "Selected Context Only" then they go away and everything is good.

If I ever close that tab, or open a fresh Chrome window, "Selected Context Only" is unchecked again.

Is it possible to get this setting persisted forever and ever?

Having exactly the same problem over the few weeks, it's driving me insane!! — 4uroraskye, Jul 01 '19 at 15:30
If I remember where this lead me, I think it's just a Chrome bug that is very very low priority for them, so don't hold your breath. :( — corysimmons, Jul 02 '19 at 05:53
Yeah, i raised another bug with them so it gained some more attention, just watching for them to do something about it now. In the mean time, i figured out that the endless console errors i am getting were actually from ghostly - so i just disabled it instead. — 4uroraskye, Aug 02 '19 at 11:11
Bug to star: https://bugs.chromium.org/p/chromium/issues/detail?id=901863 — ZachB, Mar 31 '20 at 23:39

Eduard Kolosovskyi · Answer 1 · 2022-01-31T07:52:17.087

3

You can use the filter option as a workaround. For example I was able to hide warnings like 'DevTools failed to load SourceMap: Could not load content for...' with regex -/failed\sto\sload\ssource\smap/

Also you can find a documentation for filtering here https://developers.google.com/web/tools/chrome-devtools/console/reference#filter

edited Jan 31 '22 at 07:52

answered Jun 08 '20 at 06:41

Eduard Kolosovskyi

1,396
12
18

score 1 · Answer 2 · answered May 18 '20 at 11:27

1

Selecting the same option form settings (f1) worked for me

answered May 18 '20 at 11:27

llsanketll

278
5
11

2

Hi, welcome to SO. I'm here just to give feedback on your answer to make it better. Would you be able to provide more details and links to the solution so that other devs would have a better grasp of the cause and solutions? – mjabadilla May 18 '20 at 16:11

vikbert · Answer 3 · 2020-06-12T15:00:24.567

0

I have the same problem with chrome and brave browser. To avoid showing the error messages comming from webpack dev server like the following screenshot. I defined negative filter in Console to filter them out.