Google Chrome 89 brings integration between Android phones and Chrome OS, better support for gamepads within the browser, NFC for web apps, and native web sharing. it had been released on Texas Independence Day , 2021.
Chrome OS Phone Hub for Android Devices
Google has been performing on a “Phone Hub” for Chrome OS for a touch while. The functionality is analogous to Microsoft’s “Your Phone” app on Windows 10. you’ll link your Android device and sync notifications, see recent tabs, and more.
Currently, the Phone Hub are often manually enabled through a Chrome flag. Some people saw it on Chrome 88 already, but it should be working even better on Chrome 89. you’ll see it without enabling anything after installing Chrome OS 89.
WebHID Enabled by Default
Browsers believe an equivalent HID protocol because the OS . However, an uncommon HID device, sort of a complex gamepad, may require custom logic to figure properly during a browser. This API is now enabled by default and will improve things.
Web Apps Can Use NFC
Chrome 89 on Android enables “Web NFC” by default. this suggests that web apps can now read and write NFC (Near Field Communications) tags. Typically, only native apps are ready to do that . Here may be a sample website which will scan and write NFC tags.
The above video from Google shows an internet site interacting with NFC tags using Chrome’s Web NFC API.
Native Web Sharing on the Desktop
It’s common to ascertain social network buttons on websites that allow you to simply share the page, but you’re limited to the social sites that are listed. Chrome 89 brings Windows and Chrome OS web sharing closer in line with what you see on Android.
If a site supports the new web sharing, the share button will open a native sharing menu. That way, you’ll share the link with any apps on your device that support it. You’re not just limited to a Facebook and Twitter button. Here’s a sample website that supports it.
Dropping Support for Old Processors
Starting with Chrome 89, the browser will not support older x86 processors that don’t meet the new requirements. Devices will got to meet a minimum of SSE3 (Supplemental Streaming SIMD Extensions 3).
This shouldn’t be a problem for the overwhelming majority of devices running Chrome 89 today. Processors are supporting SSE3 for on the brink of 15 years. If you are doing happen to possess one among these devices, you’ll be stuck on Chrome 88.
Chrome 89 is particularly heavy on the under-the-hood improvements and developer goodies. you’ll examine many of those changes on its developer site and therefore the Chromium blog. We’ll highlight a couple of changes here:
Debugging support for Trusted Types violations: Developers can set breakpoints and catch exceptions on Trusted Type Violations through the Sources panel.
Capture node screenshot beyond viewport: It’s now possible to capture screenshots for a full node and therefore the content below the folder from the weather panel.
New Trust Tokens tab for network requests: a replacement API called “Trust Token” can help fight fraud and distinguish bots from real people without passive tracking.
The Lighthouse panel is now running Lighthouse 7.
AVIF Image Decode: Chrome can now load AVIF content natively with AVI decoders on Android and Webview.
Cross-origin opener policy reporting API: a replacement API allows sites to trace usage across different domains.
Forced colors property: The new forced-colors CSS media query allows sites to detect whether the device is about to high-contrast display mode.