Chrome 88 was released only last week, marking the release of the Manifest V3 extension API, changes to password management, and the official death of Adobe Flash support. Chrome 89 has now arrived in the Beta Channel, and it seems to be an even bigger release — even if many of its changes are hidden to most people. Let’s dive in!
Google first announced Privacy Sandbox all the way back in 2019, as the company’s planned replacement for third-party browser cookies. It’s still very much a work in progress, but Google aims for it to be “a secure environment for personalization that also protects user privacy.” Chrome 89 has the first pieces of the personalization interface, currently hidden behind a new flag: #privacy-sandbox-settings.
With the flag enabled, a new page for Privacy Sandbox can be found in Settings > Privacy and security > Privacy sandbox. There’s currently a single toggle, which enables ‘Web crowd and ad measurement.’ Google explained how this works in a recent blog post:
Federated Learning of Cohorts (FLoC) [Privacy Sandbox] proposes a new way for businesses to reach people with relevant content and ads by clustering large groups of people with similar interests. This approach effectively hides individuals “in the crowd” and uses on-device processing to keep a person’s web history private on the browser.
By creating simulations based on the principles defined in Chrome’s FLoC proposal, Google’s ads teams have tested this privacy-first alternative to third-party cookies. Results indicate that when it comes to generating interest-based audiences, FLoC can provide an effective replacement signal for third-party cookies.
Google isn’t allowing sites to use Privacy Sandbox yet, but now we know where you’ll be able to manage its settings once the feature is finished.
Chrome 89 has a few changes to the Discover feed on the New Tab Page. Currently, articles in the Discover section are listed in cards, but in Chrome 89 they are only separated by dividers. The title font also seems to be slightly bigger, and perhaps most importantly, the description preview has been removed.
Chrome 88 (left) vs. Chrome 89 (right)
It’s interesting to see Google experiment with removing the teaser text. In most cases, they’re too short to provide any helpful context or added information, and removing them potentially allows more articles to appear on-screen at once.
Google is testing a new interface for the site info popup on Android, which appears when you press the ‘I’ or lock icon in the address bar. The popup normally shows the full address, information about page security, and a list of granted permissions. Chrome 89 includes a new flag (#page-info-discoverability) that updates the popup’s design.
Left: Old UI; Center, Right: New UI
The new popup fits in better with Google’s updated design language, and you can revoke permissions without opening Chrome’s normal settings panel.
Web NFC API
Google first began testing NFC in web apps with the release of Chrome 81. That version added initial support for the Web NFC API, allowing sites to read and write NFC tags. It’s mainly intended for inventory management, conferences, museum exhibits, and anywhere else NFC is frequently used. Starting with Chrome 89, the Web NFC API is enabled by default on Android.
Web NFC demo from Chrome Dev Summit 2019
The Web NFC API is limited to reading and writing NDEF data, so low-level operations like ISO-DEP, NFC-A/B, NFC-F are not supported. Peer-to-peer communication mode and Host-based Card Emulation (HCE) also won’t work. Unfortunately, that probably rules out any chances of someone creating an Amiibo creator web app.
Like with microphones, cameras, and other hardware features, NFC requires granting a permission from a popup. It will be interesting to see how the API will be used in the coming years.
Web Sharing on desktop
Chrome on Android has supported the Web Share and Web Share Target APIs for a while now, which allows web apps to send and receive data with Android’s native share menu. The features have gone a long way to blur the lines between native and web apps on Android, but annoyingly, they haven’t been available on desktop platforms (except with Safari on macOS)… until now.
Web sharing on Chrome OS 89
With the release of Chrome 89, web sharing (where web apps can open the system share dialog) is now available on Windows and Chrome OS, and web apps can function as a target on Chrome OS. Developers won’t have to add any extra code for the functionality to work on desktop platforms.
As always, this update includes changes for both users and developers. Here are some smaller changes included in Chrome 89:
- Chrome added support for text fragment links in 2019, which are links that automatically scroll to a certain string of text. Google Search started using them in 2020, and now websites can change how the highlighted portions look like with the new CSS ::target-text pseudo-element.
- Chrome 89 can load AVIF content natively using AV1 decoders on Android and WebView.
- The CSS property ‘list-style-type’ supports two new keywords: ‘disclosure-open’ and ‘disclosure-closed’.
- The default value of CSS ‘display’ property for
has been changed from ‘block’ to ‘list-item’.
- Chrome now supports the CSS property ‘overflow:clip,’ which allows web pages to turn off any type of scrolling for a box. It uses less RAM than ‘overflow: hidden,’ which is often used for the same purpose.
- Google has added a new cross-origin reporting API for sites to track usage across different web domains.
- Sites can now detect if the current device is set to high contrast display mode, using the new forced-colors CSS media query (similar to how detection for dark mode works).
- Some legacy prefixed events (webkitprerenderstart, webkitprerenderstop, webkitprerenderload, and webkitprerenderdomcontentloaded) have been removed.
- The chrome://media-internals page will be removed in Chrome 91, and Chrome 89 includes a new flag (#enable-media-internals) that toggles access to the page.
- The new flag #enable-table-ng is available in Chrome 89, which enables the new Blink table layout engine, TableNG.
- There’s a new flag for enabling “a rich bottom sheet” for installing Progressive Web Apps on Android, #mobile-pwa-install-use-bottom-sheet, but it doesn’t appear to do anything yet.
- When you enter a website in the Chrome address bar, it currently adds “http://” to the front by default. Chrome 89 has a new flag (#omnibox-default-typed-navigations-to-https) that changes this behavior, and if the website doesn’t appear to support HTTPS, Chrome will fall back to the HTTP URL.
- Chrome 89 has initial support for XFA forms in the PDF reader.
- A new flag, #read-later-reminder-notification, adds a popup when an article in your reading list has been unread for a week.
- The Web Serial API, which allows web apps to communicate with hardware over serial connections, is now enabled by default on Windows and Chrome OS. It was previously only enabled by default on Android.
- The WebHID API allows sites to more easily use gamepads and other interface devices, and it’s enabled by default with Chrome 89.
The APK is signed by Google and upgrades your existing app. The cryptographic signature guarantees that the file is safe to install and was not tampered with in any way. Rather than wait for Google to push this download to your devices, which can take days, download and install it just like any other APK.