Starting in 85, Chrome plans to switch its default referrer policy from no-referrer-when-downgrade to the more privacy-preserving strict-origin-when-cross-origin.
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!
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.
Implications for Web Developers and Chrome’s mitigations.
Chrome will soon mark non-secure pages containing password and credit card input fields as Not Secure in the URL bar. This document is intended to aid Web Developers in updating their sites to avoid this warning.
captureStream() method makes it possible to capture a MediaStream from a canvas, video or audio element.
Muted autoplay for video is supported on Android from Chrome 53. Previously, a video element required a user gesture to initiate playback.
From version 52, Chrome uses ECDSA by default — a much more efficient and secure algorithm for WebRTC certificate key generation. In addition, RTCCertificates can now be stored with IndexedDB.
Chrome 46 ships with a feature called HPKP reporting, which can help you roll out a stricter form of SSL for your site.