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.
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!
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.
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
Eager evaluation, argument hints, function autocompletion, Lighthouse 3.0, and more.