New issue
Advanced search Search tips
Starred by 90 users

Issue metadata

Status: Duplicate
Merged: issue 258421
Owner: ----
Closed: Jan 2014
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Feature

Sign in to add a comment

Issue 239401: Add a way to hide/filter out extension resources in the network tab of web inspector

Reported by, May 9 2013

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.0; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31

Steps to reproduce the problem:
1. Install the Readability Chrome extension (just an example, this happens with other extensions as well)
2. View an HTML page with the web inspector network tab open

What is the expected behavior?
There should be some way to filter out resources fetched using the chrome-extension:// protocol. This could be made more generic to allow filtering on any protocol, or it could simply be a 'do not show extension resources' button.

What went wrong?
Network tab lists resources from installed extensions as well as those from the current page.

Did this work before? N/A 

Chrome version: 26.0.1410.64  Channel: stable
OS Version: 6.0 (Windows Vista, Windows Server 2008)

This is a feature request rather than a bug, but listing all extension resources in addition to page resources can get very lengthy and confusing, particularly when you have a lot of extensions installed.
17.7 KB View Download

Comment 1 by, May 9 2013

Labels: -Type-Bug Type-Feature

Comment 2 by, May 23 2013

Status: Assigned

Comment 3 by, May 23 2013

 Issue 240072  has been merged into this issue.

Comment 4 by, May 23 2013

Also take care of dataURIs.

Comment 5 by, May 28 2013

 Issue 180122  has been merged into this issue.

Comment 6 by, May 31 2013

 Issue 245697  has been merged into this issue.

Comment 7 by Deleted ...@, Jan 2 2014

The filter when finding would help for now if it allowed us a way to filter by the protocol or other columns.

May I propose columName:filterstring?

Comment 8 by, Jan 7 2014

Comment elsewhere recommended using Incognito, that only works if you have the Extensions disabled in Incognito...

Comment 9 by, Jan 9 2014

Mergedinto: 258421
Status: Duplicate

Comment 10 by, Feb 19 2014

I'd like to extend the sentiment of this issue to also suppress chrome-extension:// output from Web Inspector's console log, as illustrated in this question on Super User:

Comment 11 by, Jan 15 2015

There's a way of filtering out all these requests. In the network tab filter box, use the string "-Scheme:chrome-extension" (quotes for clarity).

It would be a good thing to be able to activate this filter (or other filters) by default (as part of the configuration settings). Note that this filter will not filter the http/https requests made by an extension, if any. The real solution is for the network waterfall to have separated channels for the page and each of the extensions.

Comment 12 by, May 1 2015

A simple "hide extension resources" checkbox next to "preserve log" and "disable cache" in network view of the dev tools would do wonders here.

Comment 13 by, Jul 9 2015

A fix for this would be awesome!

Comment 14 by, Jul 27 2015

Longing for this! Vimium keeps interfering with my debugging ;-)

Comment 15 by, Jul 29 2015

Please implement a fix for this.

Comment 16 by Deleted ...@, Sep 1 2015

FInd it valueable - debugging is harder when you have several extensions with 10-20 scripts loading.
Plus it would be cool to make turn on/turn of long living - should not repeat after reload (e.g. like checkbox for cache disabling).

Comment 17 by, Jun 27 2016

Any update on this?

Comment 18 by, Jun 27 2016

Owner: ----

Comment 19 by, Sep 7 2016

It also gets annoying when the frame switches from top, to the last extension, I've had this bite me too many times lately while testing (currently a test engineer). Just to realize I'm in the wrong scope due to a random extension frame being selected :(

Comment 20 by, Oct 4 2016

Please add this feature. Especially for Console. It's really annoying for developers to change the drop down in console each time from "extension" to "top" to be able to test JS codes. (This happens when extension writes something in console). It would be nice if we can disable/filter any kind of logging from extensions.

Comment 21 by, Feb 20 2017

It is very inconvenient to insert the string each time. Please add a checkbox "hide chrome ext req"

Comment 22 by, Jun 6 2017

Please add this feature. Take care of developers)

Comment 23 by, Aug 31 2017

Any update on this? Please add a checkbox "hide chrome ext req", take care of developers.

Comment 24 by, Sep 5 2017

Please please please create this feature.  Those extensions in my network and console errors are frustrating.  Particularly Honey and LastPass.

Comment 25 by, Sep 12 2017

+1 the network monitor becomes unusable when a lot of non-related information is shown... It is a must! Thanks!

Comment 26 by, Oct 5 2017

+1 please implement this, the amount of noise in the network tab and console is growing due to extensions doing more and more and it's in the way of what people really use devtools for

Comment 27 by, Dec 19 2017

+1 for a simple checkbox option to hide extension resources!

Comment 28 by, Dec 19 2017

It would be so helpful to have a checkbox hide extension errors and messages.  Please implement and allow the checkbox to save state between sessions.  

BTW, freakin awesome tool.  It blows all the other browser tools out of the water and really helps move the web forward.

Comment 29 by, Dec 19 2017

Does this count as a feature request?

Add a way to hide/filter out extension resources in the network tab of web inspector

Comment 30 by, Jan 22 2018

Agreed - there should be a checkbox to exclude extension information from the entire dev tools UI.

Comment 31 by, Mar 31 2018

+1 please add checkbox to exclude extension resources, or persist filter

Comment 32 by, Sep 1

Agreed - there should be a checkbox to exclude extension information from the entire dev tools UI.

Comment 33 by, Nov 19

This is NOT a dupe, the work done in 2014 does not cover this case. Please reopen so this gets actioned.

Sign in to add a comment