Welcome! Here's what's new in DevTools in Chrome 60. You can check what
version of Chrome you're running at
Google I/0 '17 is a wrap. Check out Paul Irish's "DevTools: State of the Union" talk below to learn more about what the team has been working on.
New Audits panel, powered by Lighthouse
The Audits panel is now powered by Lighthouse. Lighthouse provides a comprehensive set of tests for measuring the quality of your web pages.
Check out the DevTools talk from Google I/O '17 below to learn more. Lighthouse is discussed at 32:30.
To audit a page:
- Click the Audits tab.
- Click Perform an audit.
- Click Run audit. Lighthouse sets up DevTools to emulate a mobile device, runs a bunch of tests against the page, and then displays the results in the Audits panel.
The scores at the top for Progressive Web App, Performance, Accessibility, and Best Practices are your aggregate scores for each of those categories. The rest of the report is a breakdown of each of the tests that determined your scores. Improve the quality of your web page by fixing the failing tests.
Lighthouse is an open-source project. To learn lots more about how it works and how to contribute to it, check out the Lighthouse talk from Google I/O '17 below.
Use third-party badges to get more insight into the entities that are making network requests on a page and logging to the Console.
To enable third-party badges:
- Open the Command Menu.
- Run the
Show third party badgescommand.
Use the Group by product option in the Call Tree and Bottom-Up tabs to group performance recording activity by the third-party entities that caused the activities.
A new gesture for Continue to Here
Say you're paused on line 25 of a script, and you want to jump to line 50. In the past, you could set a breakpoint on line 50, or right-click the line and select Continue to here. But now, there's a faster gesture for handling this workflow.
When stepping through code, hold Command (Mac) or Control (Windows, Linux) and then click to continue to that line of code. DevTools highlights the jumpable destinations in blue.
Step into async
A big theme for the DevTools team in the near future is to make debugging asynchronous code predictable, and to provide you a complete history of asynchronous execution.
The new gesture for Continue to Here also works with asynchronous code. When you hold Command (Mac) or Control (Windows, Linux), DevTools highlights jumpable asynchronous destinations in green.
Check out the demo below from the DevTools talk at I/O for an example.
More informative object previews in the Console
Previously, when you logged or evaluated an object in the Console, the Console
would only display
Object, which is not particularly helpful.
Now, the Console provides more information about the contents of the object.
More informative context selection menu in the Console
The Console's Context Selection menu now provides more information about available contexts.
- The title describes what each item is.
- The subtitle below the title describes the domain where the item came from.
- Hover over an iframe context to highlight it in the viewport.
Real-time updates in the Coverage tab
When recording code coverage in Chrome 59, the Coverage tab would just display Recording, with no visibility into what code was being used. Now, the Coverage tab shows you in real-time what code is being used.
Simpler network throttling options
The network throttling menus in the Network and Performance panels have been simplified to include only three options: Offline, Slow 3G, which is common in places like India, and Fast 3G, which is common in places like the United States.
The throttling options have been tweaked to match other, kernel-level throttling tools. DevTools no longer shows the latency, download, and upload metrics next to each option, because those values were misleading. The goal is to match the true experience of each option.
Async stacks on by default
The Async checkbox has been removed from the Sources panel. Async
stack traces are now on by default. In the past, this option was opt-in,
because of performance overhead. The overhead is now minimal enough to enable
the feature by default. If you prefer to have async stack traces disabled,
you can turn them off in Settings or by running the
capture async stack traces command in the Command Menu.
The best place to discuss any of the features or changes you see here is the firstname.lastname@example.org mailing list.
That's all for what's new in DevTools in Chrome 60. See you in 6 weeks!