Multi-client remote debugging, push notifications with custom data, and Workspaces 2.0.
Chrome 64 can experimentally disable hardware noise suppression when using the WebRTC echo canceller, to improve audio quality.
Yesterday, the Coalition for Better Ads announced the "Better Ads Experience Program." This Program provides guidelines for companies on how they can use the Better Ads Standards to help improve users' experience with ads on the web.
The non-standard chrome.loadTimes() API will be deprecated in Chrome 64 now that standards-based equivalents exist for all of its useful features.
Today, we’re announcing a new Chrome User Experience Report with expanded coverage of over 1 million top origins on the web.
A round up of the deprecations and removals in Chrome 64 to help you plan. In this version, performance API changes, removal of support for multiple shadow roots, and removal of a WebKit API.
New performance audits, a rehaul of the accessibility score, report UX improvements, and bug fixes.
Predictable media playback, HDR on Windows 10, offline playback with persistent licenses, and more are waiting for you in Chrome 64.
The Device Memory API allows developers to serve different resources to users based on their device's memory capabilities.
Performance Monitor, Console Sidebar, and Console groupings.
The CSS overscroll-behavior property allows developers to override the browser's overflow scroll effects when reaching the top/bottom of content. It can be used to customize or prevent the mobile pull-to-refresh action.
Say goodbye to shadow-piercing CSS selectors.
A round up of the deprecations and removals in Chrome 63 to help you plan. In this version, new behavior on interface properties, removal of a webkit function, and a change to
There are several ways to deal with
Five new audits, the chrome-launcher standalone Node module, and a new throttling guide.
Chrome 62 improves the network information API with network quality indicators, support for OpenType Variable Fonts has landed and you can now capture and process media streams from HTMLMediaElements with the Media Capture from DOM elements API.
A few tricks are necessary to animate a blur efficiently.
Aborting fetches using a new web primitive – The abort controller
Learn about what is changing in the WebVR API
position: sticky and
IntersectionObserver together to determine when elements become sticky. Apply scroll effects without scroll events!
Sensors are used in many native applications to enable advanced features. Wouldn't it be nice to bridge the gap between native and the web? You can do it with Generic Sensor API, which is enabled by default in Chrome 67 or later.
A round up of the deprecations and removals in Chrome 62 to help you plan. In this version, more restrictions on insecure origins and a change to the shadow-piercing descendant combinator.
Learn best practices for good user experiences with the new autoplay policies in Chrome, coming April 2018.
Let's discuss a Web API that would allow websites to create a floating video window over the desktop
Offline playback with persistent licenses and Widevine L1 on Android, video track optimizations, automatic video fullscreen when device is rotated, customizable seekable range on live MS streams, FLAC in MP4 with MSE are here!
The visual viewport API gives you details on how the user zooms and scrolls around your page.
Top-level await operators in the Console, new screenshot workflows, CSS Grid highlighting, and more.
A round up of the deprecations and removals in Chrome 61 to help you plan. In this version, more restrictions on insecure origins and a change to the shadow-piercing descendant combinator.
navigator.storage.estimate() gives you insight into your web app's storage constraints.
Background video track optimizations and automatic video fullscreen when device is rotated are here!
With Chrome 60, you can now measure time to first paint and time to first contentful paint with the Paint Timings API. You can control how fonts are rendered with the font-display CSS property. WebAssembly has landed and there's plenty more!
New features and changes coming to DevTools in Chrome 61.
Providing a smooth user experience is important for the web. Over the past few releases of Chrome we have driven down input latency across these devices.
“Code splitting” and “route-based chunking” are some of the new buzzwords in web development. But what do they mean and how can you implement them?
What is really happening with "DOMException: The play() request was interrupted"?
How to setup Karma, Mocha+Chai, and Travis to run automated tests on Headless Chrome.
Latest updates coming to the Credential Management API in Chrome 60. Also includes an update landed in Chrome 57.
A round up of the deprecations and removals in Chrome 60 to help you plan. In this version, security improvements, further webkit deprecations, and more.
The Budget API allows developers to perform background actions without notifying users, enabling use cases like silent push.
With Chrome 59, you can run Chrome in an automated environment without a user interface or peripherals; notifications on macOS are shown directly by the native macOS notification system; you can now capture full resolution photos with the image capture API, and there’s plenty more!
New features and changes coming to DevTools in Chrome 60.
A round up of the deprecations and removals in Chrome 59 to help you plan.
Headless Chrome (shipping in Chrome 59) is a way to run the Chrome browser in a headless environment. It brings all modern web platform features provided by Chromium and the Blink rendering engine to the command line.
As of Chrome 59, notifications will be displayed native notifications on macOS.
With Chrome 58, Progressive Web Apps are more immersive with display: fullscreen. IndexedDB 2.0 is now supported and sandboxed iFrames get more options. Pete LePage has all the details and how you can use these new developer features in Chrome 58.
New features and changes coming to DevTools in Chrome 59.
When making expand and collapse effects you can use scale transforms to keep your UI performant.
Custom transform matrices allow you to build frame-perfect custom scrollbars.
Media controls customization, Autoplay for Progressive Web Apps added to the home screen, pause the autoplaying of muted video when invisible, and color-gamut media query are there!
Today, when using Media Source Extensions (MSE) in Chrome, it's not possible to switch between encrypted and clear streams. Starting in Chrome 58, all this changes.
A round up of the deprecations and removals in Chrome 58 to help you plan.
Background tabs can have a dramatic negative effect on battery life. Chrome 57 brings new power saving changes to background tab behavior by throttling timers if a page is using too much CPU.
With Chrome 57, you can now use
display: grid for grid based layouts, use the media session API to customize the lock screen and notifications with information about the media being played, and more. Pete LePage has all the details and how you can use these new developer features in Chrome 57!
New features and changes coming to DevTools in Chrome 58.
Navigation preload lets you overcome service worker startup time by making requests in parallel.
What's new in Lighthouse 1.5. New audits, extension updates, Performance Experiment, online Viewer features, and UI tweaks.
Finally! We can customize web media notifications (title, artist, album name, artwork) and respond to media related events such as seeking or track changing with the new Media Session API.
A round up of the deprecations and removals in Chrome to help you plan.
In Chrome, there are updates to the Payment Request API following the spec changes. Learn what they are and make changes to your own implementation.
CSS Grid Layout makes creating two dimensional grid based layouts easy. It's been in development for over 5 years, but is now available in Chrome and coming to other browsers soon. Let's take a peek at what's new and how you can use it on your sites!
With Chrome 56, web apps can now communicate with nearby Bluetooth Low Energy devices using the Web Bluetooth API. CSS
position: sticky; is back - making it easy to create elements that scroll normally until sticking to the top of the viewport. And HTML5 by Default is enabled for all users.
Scrolling responsiveness is critical to the user's engagement with a website on mobile, yet touch event listeners often cause serious scrolling performance problems. Learn how we are helping users and developers to be fast by default.
Web Components are gaining cross-browser support, the community is growing in leaps and bounds, and there’s a brand-new Web Component catalog to find exactly the component you need.