New in Chrome 60
- Paint Timing API allows you to measure time to first paint and time to first contentful paint with the Paint Timings AP.
font-displayallows you to control how fonts are rendered before they're downloaded.
- WebAssembly has landed
- And there's plenty more!
Want the full list of changes? Check out the Chromium source repository change list
I'm Pete LePage. Let's dive in and see what's new for developers in Chrome 60!
Paint timings API
When a user navigates to a web page, they're look for some visual feedback to reassure them that everything is working. With the new paint timings API, we can now measure that.
The API exposes two metrics:
- Time to first paint - which marks the point when the browser starts to render something, the first bit of content on the screen.
- Time to first contentful paint - which marks the point when the browser renders the first bit of content from the DOM, text, an image, etc.
Check out Leveraging the Performance Metrics that Most Affect User Experience to learn how you can track these metrics and use them to improve your experience.
Web Fonts give you the ability to incorporate rich typography. But, if the user doesn't already have the typeface, it needs to be downloaded, potentially making your site appear slow.
Thankfully, most browsers will use a fallback if the font takes too long to download. The new
font-display property, allows you to control how a downloadable font renders before it's fully loaded.
autouses whatever font display strategy the user-agent uses.
blockgives the font face a short block period and an infinite swap period.
swapgives the font face a zero second block period and an infinite swap period.
fallbackgives the font face an extremely small block period and a short swap period.
optionalgives the font face an extremely small block period and a zero second swap period.
It's supported in Chrome 60 and Opera, and is in development on Firefox. Check out Controlling Font Performance with
font-display for more information.
Web Assembly or wasm provides a new way to run code, written in languages like C and C++ on the web, at near native speed.
It provides the speed necessary to build an in-browser video editor or to run a Unity game at a high frame rate utilizing existing standards-based web platform APIs.
You can find more info at webassembly.org, including demos, docs and how to get started.
- The new Web Budget API enables sites with the Push Notification permission to send a limited number of push messages that trigger background work such as syncing data or dismissing notifications, without the need to show a user-visible notification.
PushSubscription.expirationTimeis now available, notifying sites when and if a subscription will expire.
- Object rest & spread properties are now supported, making it simpler to merge and shallow-clone objects and implement various immutable object patterns.
Note: The Payment Request API was pushed to Chrome 61.
These are just a few of the changes in Chrome 60 for developers.
I'm Pete LePage, and as soon as Chrome 61 is released, I'll be right here to tell you -- what's new in Chrome!