4 ms·
I still would prefer the resources tab to split between css/js/images instead of just one giant list of all the resources (including XHR)
by HaloZero 16y ago
I still would prefer the resources tab to split between css/js/images instead of just one giant list of all the resources (including XHR)
- masklinn 16y agoThe mixed tab is not "resources" anymore, it's "network" and it's filtrable by type. XHRs don't appear in the new "Resources" tab.
- HaloZero 16y agoBut the Network tab only shows you files if you had it opened from the start, which is of coures correct behavior. You don't want Chrome tracking network latencies on all sites you load. The network tab is for tracking more than looking at resources.
- yesimahuman 16y agoYea I don't understand the resources tab. It's just a mess right now with a huge list of files. It seems like it would be a good place to list what stylesheets were loaded and such, but it seems like the network tab has taken over most of that. I say get rid of it or rename it and move it to the end of the tab list, considering how useless it is for the majority of cases.
- HaloZero 16y agoI think they future cased it for HTML storage requirements and for people who are doing more advanced stuff rather than just basic work. Might be useful if you're using those features.
- masklinn 16y agoResources is a list of all the resources linked to the current tab (page). It starts with a nested trees of network resources (Frames > Pages > HTML, CSS, JavaScript and Images, note that in the case of e.g. CSS files if you have performed editions via the Elements tab they will be trees as well listing all previous revisions of the file), then lists the databases, local storage, session storage, cookies and application cache for the page. Networks holds most of the old "Resources" tab, it is a detailed view of the network transactions (HTTP and WebSocket request/responses) performed on the current page since it was opened.