A round up of the deprecations and removals in Chrome 80 to help you plan.
WebVR 1.1 has been removed from Chrome.
Support for let and class redeclarations in the Console, improved WebAssembly debugging, and more.
Step over code, set breakpoints, and resolve stack traces in your source languages from within DevTools.
A round up of the deprecations and removals in Chrome 79 to help you plan.
Debug why cookies were blocked, simulate "prefers-color-scheme: dark", code coverage updates, and more.
A round up of the deprecations and removals in Chrome 78 to help you plan.
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. Also, updates to imported scripts can trigger the service worker update flow.
Lighthouse 5.2 in the Audits panel, and Largest Contentful Paint in the Performance panel.
This article is about me playing with the experimental WebGPU API and sharing my journey with web developers interested in performing data-parallel computations using the GPU.
A round up of the deprecations and removals in Chrome 77 to help you plan.
Copy element styles, visualize layout shifting, and more.
A round up of the audio/video updates in Chrome 75: predicting whether playback will be smooth and power efficient for encrypted media and support of the video element's "playsInline" attribute hint.
Web Components v0 users have more time to upgrade to v1; but be sure and test.
A round up of the deprecations and removals in Chrome 76 to help you plan.
When a Progressive Web App is installed on Android, Chrome automatically requests and installs a WebAPK of your app. Starting in Chrome 76, Chrome will check for updates more frequently, ensuring icons, titles, colors, and other key properties to rolled out to your users faster.
In Chrome 76, we're making it easier for users to install Progressive Web Apps on the desktop by adding an install button to the address bar. If a site meets the Progressive Web App installability criteria, Chrome will automatically show an install icon in the address bar, making it easy for users to install your PWA.
LayoutNG is a new layout engine for Chromium that has been designed for the needs of modern scalable web applications. It improves performance isolation, better supports scripts other than Latin, and fixes many float, margin, and web compatibility issues.
If your PWA has use cases where it’s helpful for a user to install your app, for example if you have users who use your app more than once a week, you should be promoting the installation of your PWA within the web UI of your app. We have new recommendations on how you can promote the installation of your app.
Autocomplete with CSS values, a new UI for network settings, and more.
We're giving you more control over the PWA Add to Home Screen mini-infobar. Starting in Chrome 76, you can prevent the mini-infobar from appearing by calling
preventDefault() on the
In February, we introduced the model-viewer web component which let you declaratively add a 3D model to a web page. Now we're announcing support for AR on Android with the addition of the ar attribute.
A quick overview of paint holding. A Chromium feature for reducing the flash of white on same-origin navigations
A round up of the deprecations and removals in Chrome 75 to help you plan.
Stylus-based drawing applications built for the web suffer from latency issues because a web page has to synchronize graphics updates with the DOM. The desynchronized hint for contexts bypasses the DOM to eliminate the latency.
Meaningful autocomplete preset values, clear site data from the Command Menu, and more.
A round up of the deprecations and removals in Chrome 74 to help you plan.
An introduction to the new KV Storage API, built-in modules, and import maps.
Highlight nodes affected by a CSS property, Lighthouse v4, WebSocket binary message viewer, and more.
February wrap up which we look back what's been happening in Web Developer Ecosystem team.
Intersection Observer v2 adds the capability to not only observe intersections per se, but to also detect if the intersecting element was visible at the time of intersection.
Priority Hints are coming to an Origin Trial near you! Try them out!
Shipping in Chrome 73, Constructable Stylesheets provide a seamless way to create and distribute styles to documents or shadow roots without worrying about FOUC.
A round up of the deprecations and removals in Chrome 73 to help you plan.
Scrolling responsiveness is critical to the user's engagement with a website on mobile, yet
wheel event listeners often cause serious scrolling performance problems. Learn how we are helping users and developers to be fast by default.
Chrome 73 introduces the
String.prototype.matchAll() method. It behaves similarly to
match(), but offers a simple way to iterate over matches, especially when you need access to capture groups.
Adding 3D models to a website can be tricky for a variety of reasons including the hosting issues and the high bar of 3D programming. That's why we're introducing the
<model-viewer> web component to let you use 3D models declaratively.
Where should we implement logic and rendering in our applications? Should we use Server Side Rendering? What about Rehydration? Let's find some answers!
A round up of the audio/video updates in Chrome 73: Hardware media keys support, HDCP policy check, Picture-in-Picture origin trials, and more.
lit-html and LitElement are two new libraries for building fast, interoperable components. lit-html provides lightning-fast templating. LitElement is a lightweight base class for building Web Components with lit-html templates.
The RTCQuicTransport is a new web platform API that allows exchanging arbitrary data with remote peers using the QUIC protocol.
Instead of only surfacing generalized advice, Stack Packs will extend Lighthouse to include additional messages for specific tools.
Logpoints, detailed tooltips in Inspect Mode, and much more.
How do you integrate WebAssembly into this setup? In this article we are going to work this out with C/C++ and Emscripten as an example.
In version 72, Chrome ships User Activation v2 which makes user activation availability complete for all activation-gated APIs, resolving many user activation inconsistencies.