As the capability gap between web and native gets smaller, it becomes easier to offer the same experience for both web and native users. This may lead to cases where users have both the web and native versions installed on the same device. Apps should be able to detect this situation. The
getInstalledRelatedApps API is a new web platform API that allows your web app to check to see if your native app is installed on the users device, and vice versa.
A round up of the deprecations and removals in Chrome 72 to help you plan.
To avoid draining the battery, most devices will quickly fall asleep when left idle. While this is fine for most of the time, there are some applications that need to keep the screen or the device awake in order to complete some work. The Wake Lock API provides a way to prevent the device from dimming or locking the screen or prevent the device from going to sleep when an application needs to keep running.
Intl.ListFormat API enables localized formatting of lists without sacrificing performance.
The Badging API is a new web platform API that allows installed web apps to set an application-wide badge, shown in an operating-system-specific place associated with the application, such as the shelf or home screen. Badging makes it easy to subtly notify the user that there is some new activity that might require their attention, or it can be used to indicate a small amount of information, such as an unread count.
The Web Share Target API allows installed web apps to register with the underlying OS as a share target to receive shared content from either the Web Share API or system events, like the OS-level share button.
Chrome 71 makes displaying relative time values easier with the new
Intl.RelativeTimeFormat() API. You can specify which side of the text the underline should appear on for text that flows vertically. And using the speech synthesis API now requires user activation before your computer starts talking to you! Let’s dive in and see what’s new for developers in Chrome 71!
Background Fetch lets you handle large downloads, even if the browser closes.
Visualize performance metrics, highlight text nodes, copy the JS path to a node, and Audits panel updates.
A recap of our Web Audio autoplay policy changes which are rolling out soon in Chrome.
We strongly believe that every developer should have access to the capabilities they need to make a great web experience, and we are committed to a more capable web. Learn about some of the new APIs we're considering and how you can get involved.
The writable files API is being designed to increase interoperability of web applications with native applications, making it possible for users to choose files or directories that a web app can interact with on the native file system.
Signed Exchanges allow websites to sign web content in the way that the content can be safely redistributed and verified where it was originally from.
WebAssembly threads enable an application to make use of parallel threads running while sharing the same memory address space. This enables libraries and applications that rely on pthreads to be ported to run in the browser. This feature is being run under an origin-trial to solicit feedback from the developer community.
A round up of the deprecations and removals in Chrome 71 to help you plan.
Intl.RelativeTimeFormat API enables localized formatting of relative times without sacrificing performance.
Control Picture-in-Picture for video elements on your website.
Chrome 70 adds support for Desktop Progressive Web Apps on Windows and Linux, support for Public Key Credentials to the Credential Management API, allows you to provide a
name to dedicated
workers and plenty more. Let’s dive in and see what’s new for developers in Chrome 70!
Some small changes are coming to
importScripts(), starting in Chrome 71.
Chrome 69 includes an incorrect change to our paint-timing metrics, which was intended to capture more of the rendering pipeline, but resulted in some inaccurate timestamps.
Highlight DOM nodes from Live expressions, store nodes as global variables, and more.
Animation Worklet allows you to write imperative animations that run at the device's native frame rate for that extra buttery jank-free smoothness™, make your animations more resilient against main thread jank and are linkable to scroll instead of time.
For the last of this 4 part blog series, we look at how the compositor is enabling smooth interaction when user input comes in
Once the browser receives page data, what happens inside of the renderer process to display a page?
A round up of the audio/video updates in Chrome 70: AV1 decoder, cross-codec and cross-bytestream buffering and playback, Opus in MP4 with MSE, and protected content playback allowed by default on Android.
A round up of the deprecations and removals in Chrome 70 to help you plan.
When you type a URL into the address bar, what happens after? When are security checks done and how does the browser speed up the process? Let's look at the page navigation process in browser!
The Cookie Store API offers asynchronous access to HTTP cookies, and opens up the cookie jar to service workers.
Learn how browser turn your code into functional website from high-level architecture to the specifics of the rendering pipeline. In part 1, we’ll take a look at core computing terminology and Chrome’s multi-process architecture.
It’s been ten years since Chrome was first released. A lot has changed since then, but our goal of building a solid foundation for modern web applications hasn’t! In Chrome 69 there’s support CSS Scroll Snapping, support for notches, web locks, and a few cool new CSS4 features. Let’s dive in and see what’s new for developers in Chrome 69!
Reporting API brings a common infrastructure for the browser to send reports for various issues: CSP violations, deprecations, browser interventions, network errors, and feature policy violations.
Live Expressions in the Console, highlight DOM nodes during Eager Evaluation, and more.
WebAssembly lets us extend the browser with new features. This article shows how to port the AV1 video decoder and play AV1 video in any modern browser.
Learn the current tools, libraries and optimization techniques that make improving web performance easier, by following the Oodles Theater project.
OffscreenCanvasAPI is available as of Chrome 69. This article explains how you can use it to achieve performance improvements in rendering graphics in your web app.
Today we're releasing the CrUX Dashboard that you can use to better understand how an origin's performance evolves.
A round up of the deprecations and removals in Chrome 69 to help you plan.
A round up of the audio/video updates in Chrome 69: AV1 and HDCP policy check.
ReportingObserver gives developers insight into what their code is doing in the wild. ReportingObserver surfaces information on issues like deprecations and interventions, messages that were previously only available in the DevTools console.
Speed is now a landing page factor for Google Search and Ads.
The Page Lifecycle API brings app lifecycle features common on mobile operating systems to the web. Browsers are now able to safely freeze and discard background pages to conserve resources, and developers can safely handle these interventions without affecting the user experience.
Chrome 68 brings changes to the Add to Home Screen behavior on Android, giving you more control. The page lifecycle API tells you when your tab has been suspended or restored. And the Payment Handler API makes it possible for web-based payment apps to support the Payment Request experience. Let’s dive in and see what’s new for developers in Chrome 68!
Chrome 63 shipped with NoState Prefetch. NoState Prefetch is a mechanism for fetching resources in advance that uses less memory than the deprecated prerendering process.
Use the PWACompat library to bring your Web App Manifest to all browsers. By simply dropping in the library, many of the
meta meta tags required to support older browsers for icons, home screen behavior, theming etc, will be added automatically- no more steps required!
Chrome 67 on desktop has a new feature called Site Isolation enabled by default. This article explains what Site Isolation is all about, why it’s necessary, and why web developers should be aware of it.
Announcing the addition of the First Input Delay (FID) experimental metric to the Chrome User Experience Report.
Feature Policy allows developers to selectively enable, disable, and modify the behavior of certain APIs and features in the browser. It's like CSP, but for features! Shipped in Chrome 60.
A new Origin Trial is run in Chrome M68, which adds support for more native echo cancellers, as well as a constraint to control them.
Advanced design patterns to unlock Audio Worklet's fullest power with WebAssembly and SharedArrayBuffer.
Augmented reality allows placement and tracking of virtual objects in a real-world view.
Chacmool, an educational web demo, shows how easily web based AR can build an engaging experience.
A round up of the deprecations and removals in Chrome 68 to help you plan.
Chrome beta 68 ships with the Payment Handler API -- the new, open, and standard way for web-based payment applications to be offered as a payment option during checkout. It enables merchants to accept a wide variety of payment options within a native-browser experience.
Starting in Chrome 68 on Android, the Add to Home Screen behavior is changing to give you more control over when and how to prompt the user. If your site meets the add to home screen criteria, Chrome will no longer automatically show the add to home screen banner. Instead, you'll need to call
prompt() on the saved
beforeinstallprompt event to show the add to home screen dialog prompt to your users
Starting in Chrome 68, HTTP requests that check for updates to the service worker script will no longer be fulfilled by the HTTP cache by default. This works around a common developer pain point, in which setting an inadvertent
Cache-Control: header on your service worker script could lead to delayed updates.
Chrome 67 brings Progressive Web Apps to the desktop. Adds support for the generic sensor API, which makes it way easier to get access to device sensors like the accelerometer, gyroscope and more. And adds support for BigInts making dealing with big integers way easier. Let’s dive in and see what’s new for developers in Chrome 67!
Building a Progressive Web App doesn't mean building a single page app! Read about alternative architectures for content-focused PWAs, and help you make the right decision for your specific use case.
Eager evaluation, argument hints, function autocompletion, Lighthouse 3.0, and more.
Chrome 67 beta introduces the Web Authentication (WebAuthn) API, which allows browsers to interact with and manage public-key based credentials. This enables strong authentication using removable security keys and built-in platform authenticators such as fingerprint scanners.
First Input Delay (FID) is a new performance metric for measuring page responsiveness for real users in the wild.
The immersive web means virtual world experiences hosted through the browser. This entire virtual reality experiences surfaced in the browser or in VR enabled headsets.
New perf audits for preload, preconnect, GIFs, and more.
Faster audits, less variance, a new report UI, new audits, and more.
A round up of the deprecations and removals in Chrome 67 to help you plan. In this version, deprecation of public key pinning, removal of AppCache on unsecure contexts, and more prefix removals.
Search across network headers, copy requests as fetch, audit pages using desktop conditions, and much more.
Chrome 66 allows web pages to use a secondary attached display through the Presentation API and to control its contents through the Presentation Receiver API.
CSS Typed Object Model (Typed OM) brings types, methods, and a flexible object model to working with CSS values. Shipped in Chrome 66.
A round up of the deprecations and removals in Chrome 66 to help you plan. In this version, improved service worker security, changes to CSS position values, and more.
Since version 10.12 (Sierra), macOS includes a native echo canceller. Here's how you can try it out in Chrome!
What can #SmooshGate teach us about standards development and the Web Platform? This write-up gives an overview.
Credential Management API Feature Detection Check-up
Async Clipboard API simplifies permissions-friendly copy & paste.
Chrome 65 adds support for the new CSS Paint API, which allows you to programmatically generate an image. You can use the Server Timing API to provide server performance timing information via HTTP headers, and the new CSS display: contents property can make boxes disappear! Let’s dive in and see what’s new for developers in Chrome 65!
Wasm allows you to run C code on the web.
Blackboxing in the Network panel, auto-adjust zooming in Device Mode, and more.
New perf and SEO audits, perf as the first section in reports, and more.
A round up of the deprecations and removals in Chrome 65 to help you plan. In this version, a reminder about Symantec certificates, cross-origin downloads are blocked, and
document.all is now read only.
Implications for Web Developers and Chrome’s mitigations.
Announcing the release of a new country dimension in the Chrome User Experience Report.
Chrome 64 adds support for ResizeObservers, which will notify you when an element’s content rectangle has changed its size. Modules can now access to host specific metadata with import.metadata The pop-up blocker gets strong and plenty more. Let’s dive in and see what’s new for developers in Chrome 64!
Use Puppeteer to launch Chromium with DevTools features enabled.
Houdini’s CSS Paint API allows you to programmatically draw CSS images.
Local Overrides, accessibility tools, performance and SEO audits, and more.
New SEO audits and manual accessibility audits, and updates to the WebP audit.