What's New In DevTools (Chrome 73)

By Kayce Basques

Technical Writer, Chrome DevTools & Lighthouse

Here's what's new in DevTools in Chrome 73.

Logpoints

Use Logpoints to log messages to the Console without cluttering up your code with console.log() calls.

To add a logpoint:

Right-click the line number where you want to add the Logpoint.

Figure 1. Adding a Logpoint
Select Add logpoint. The Breakpoint Editor pops up.

Figure 2. The Breakpoint Editor
In the Breakpoint Editor, enter the expression that you want to log to the Console.

Figure 3. Typing the Logpoint expression

Tip! When logging out a variable (e.g. TodoApp), wrap the variable in an object (e.g. {TodoApp}) to log out its name and value in the Console. See Always Log Objects and Object Property Value Shorthand to learn more about this syntax.
Press Enter or click outside of the Breakpoint Editor to save. The orange badge on top of the line number represents the Logpoint.

Figure 4. An orange Logpoint badge on line 174

The next time that the line executes, DevTools logs the result of the Logpoint expression to the Console.

**Figure 5**. The result of the Logpoint expression in the Console

See Chromium issue #700519 to report bugs or suggest improvements.

Detailed tooltips in Inspect Mode

When inspecting a node, DevTools now shows an expanded tooltip containing commonly important information like font size, font color, contrast ratio, and box model dimensions.

To inspect a node:

Click Inspect .

Tip! Hover over Inspect to see its keyboard shortcut.
In your viewport, hover over the node.

Export code coverage data

Code coverage data can now be exported as a JSON file. The JSON looks like this:

[
  {
    "url": "https://wndt73.glitch.me/style.css",
    "ranges": [
      {
        "start": 0,
        "end": 21
      },
      {
        "start": 45,
        "end": 67
      }
    ],
    "text": "body { margin: 1em; } figure { padding: 0; } h1 { color: #317EFB; }"
  },
  ...
]

url is the URL of the CSS or JavaScript file that DevTools analyzed. ranges describes the portions of the code that were used. start is the starting offset for a range that was used. end is the ending offset. text is the full text of the file.

In the example above, the range 0 to 21 corresponds to body { margin: 1em; } and the range 45 to 67 corresponds to h1 { color: #317EFB; }. In other words, the first and last rulesets were used and the middle one was not.

To analyze how much code is used on page load and export the data:

Press Control+Shift+P or Command+Shift+P (Mac) to open the Command Menu.

Figure 7. The Command Menu
Start typing coverage, select Show Coverage and then press Enter.

Figure 8. Show Coverage

The Coverage tab opens.

Figure 9. The Coverage tab
Click Reload . DevTools reloads the page and records how much code is used compared to how much is shipped.
Click Export to export the data as a JSON file.

Code coverage is also available in Puppeteer, a browser automation tool maintained by the DevTools team. See Coverage.

See Chromium issue #717195 to report bugs or suggest improvements.

Navigate the Console with the keyboard

You can now use the keyboard to navigate the Console. Here's an example.

Pressing Shift+Tab focuses the last message (or result of an evaluated expression). If the message contains links, the last link is highlighted first. Pressing Enter opens the link in a new tab. Pressing the Left arrow key highlights the entire message (see Figure 13).

Pressing the Up arrow key focuses the next link.

Pressing the Up arrow key again focuses the entire message.

**Figure 13**. Focusing an entire message

Pressing the Right arrow key expands a collapsed stack trace (or object, array, and so on).

**Figure 14**. Expanding a collapsed stack trace

Pressing the Left arrow key collapses an expanded message or result.

See Chromium issue #865674 to report bugs or suggest improvements.

AAA contrast ratio line in the Color Picker

The Color Picker now shows a second line to indicate which colors meet the AAA contrast ratio recommendation. The AA line has been there since Chrome 65.

**Figure 15**. The AA line (top) and AAA line (bottom)

Colors between the 2 lines represent colors that meet the AA recommendation but do not meet the AAA recommendation. When a color meets the AAA recommendation, anything on the same side of that color also meets the recommendation. For example, in Figure X anything below the lower line is AAA, and anything above the upper line does not even meet the AA recommendation.

See Contrast ratio in the Color Picker to learn how to access this feature.

See Chromium issue #879856 to report bugs or suggest improvements.

Save custom geolocation overrides

The Sensors tab now lets you save custom geolocation overrides.

Press Control+Shift+P or Command+Shift+P (Mac) to open the Command Menu.

Figure 16. The Command Menu
Type sensors, select Show Sensors, and press Enter. The Sensors tab opens.

Figure 17. The Sensors tab
In the Geolocation section click Manage. Settings > Geolocations opens up.

Figure 18. The Geolocations tab in Settings
Click Add location.
Enter a location name, latitude, and longitude, then click Add.

Figure 19. Adding a custom geolocation

See Chromium issue #649657 to report bugs or suggest improvements.

Code folding

The Sources and Network panels now support code folding.

**Figure 20**. Lines 54 to 65 have been folded

To enable code folding:

Press F1 to open Settings.
Under Settings > Preferences > Sources enable Code folding.

To fold a block of code:

Hover your mouse over the line number where the block starts.
Click Fold .

See Chromium issue #328431 to report bugs or suggest improvements.

Messages tab

The Frames tab has been renamed to the Messages tab. This tab is only available in the Network panel when inspecting a web socket connection.

See Chromium issue #802182 to report bugs or suggest improvements.

Feedback

Was this page helpful?

Yes

What was the best thing about this page?

It helped me complete my goal(s)