Skip to content

Latest commit

 

History

History
164 lines (98 loc) · 7.2 KB

File metadata and controls

164 lines (98 loc) · 7.2 KB
title View page resources
description Organize resources by frame, domain, type, or other criteria.
author MSEdgeTeam
ms.author msedgedevrel
ms.topic conceptual
ms.prod microsoft-edge
ms.date 05/04/2021

View page resources

Resources are the files that a page needs in order to display correctly. Examples of resources include:

  • CSS files.
  • JavaScript files.
  • HTML files.
  • Image files.

You can view the resources that make up a web page from within several tools, or panels.

This guide assumes that you are familiar with the basics of web development and Microsoft Edge DevTools.

Open resources from the Command Menu

When you know the name of the resource that you want to inspect, the Command Menu provides a fast way of opening the resource.

  1. Press Ctrl+P (Windows, Linux) or Command+P (macOS). The Open File dialog opens.

    The Open File dialog.

  2. Select the file from the dropdown list, or start typing the filename and press Enter once the correct file is highlighted in the autocomplete box.

    Type a filename in the Open File dialog.

Open resources in the Network tool

See Inspect the details of a resource in Inspect network activity.

Inspect a resource in the Network tool.

Reveal resources in the Network tool from other panels

The next section, Browse resources in the Network panel, shows how to view resources from various parts of the DevTools UI. To inspect a resource in the Network tool, right-click the resource and select Reveal in Network panel.

Revealing resources in the Network panel.

Browse resources in the Network panel

  1. Open Log network activity (in the article Inspect network activity) in a new tab or window.

Page resources in the Network Log.

Browse resources by directory in the Sources tool

To view the resources of a webpage organized by directory:

  1. Open DevTools.

  2. Select the Sources tool, and then in the Navigator pane in the upper left, select the Page tab.

  3. Click the More options (...) button to the right of the Page tab, and then select Group by folder.

    The Page tab in the Navigator pane of the Sources tool.

    Here is a breakdown of the non-obvious items in the previous figure.

    Page item Description
    top The main document browsing context.
    airhorner.com The domain. All resources nested under it come from that domain. For example, the full URL of the comlink.global.js file is probably https://airhorner.com/scripts/comlink.global.js.
    scripts A directory.
    (index) The main HTML document.
    sw.js A service worker runtime context.
  4. Select a resource to view it in the Editor.

    View a file in the Editor.

Browse resources by filename in the Sources tool

By default, the Page tab groups resources by directory. To display the resources for each domain as a flat list, instead of grouping them by directory:

  1. Go to the Sources tool.

  2. In the Navigator pane (on the left), select the Page tab.

  3. Click More options ... and then clear the Group by folder checkbox.

    The Group by folder option.

    Resources are organized by file type. Within each file type, the resources are organized alphabetically.

    The Page tab after clearing the Group by folder check mark.

Browse resources by file type in the Application tool

To group resources together based on their file type:

  1. Select the Application tab. The Application tool opens. By default, the Manifest pane usually opens first.

    The Application tool.

  2. Scroll down to the Frames pane.

    The Frames pane.

  3. Expand the sections you're interested in.

  4. Select a resource to view it.

    View a resource in the Application panel.

Browse files by type in the Network panel

See Filter by resource type.

Filter for CSS in the Network Log.

Note

Portions of this page are modifications based on work created and shared by Google and used according to terms described in the Creative Commons Attribution 4.0 International License. The original page is found here and is authored by Kayce Basques (Technical Writer, Chrome DevTools & Lighthouse).

Creative Commons License. This work is licensed under a Creative Commons Attribution 4.0 International License.