Chrome 88 was released on January 19, 2021 and several days later, Google announced the launch of the beta version of Chrome 89 for developers to test.
Chrome 89 beta has many additions, especially new web APIs and other Notable new features that web developers can start using. The new features include various APIs for interacting with hardware, for example Chrome 89 beta has a desktop sharing API for Windows and Chrome OS, but Mozilla and Apple consider many of these features to be harmful.
What are the new features that will be introduced in Google Chrome 89?
Chrome 89 entered beta on January 28 and Google launched it immediately. If Google sticks to its schedule, Chrome 89 should be stable in about a month, early March.
According to the Google Chromium team, there is a long list of human interface devices (HID) that are too recent, too old, or too rare so that system controllers can access them.
Basically the main motivation for WebHID has been to provide better support for gamepads in browsers.
Another change is in NFC (Near Field Communications), Web NFC enables a web application to read and write on NFC badges when they are moved close to the user's device (typically 5-10 cm, 2-4 inches). The current scope is limited to NDEF, a lightweight binary message format.
Another new feature is the Web Serial API. It is a serial port, that is, a bidirectional communication interface that allows you to send and receive data byte by byte. The Web Serial API brings this capability to websites, allowing them to control devices with serial ports, including microcontrollers and 3D printers.
In fact, the Chromium team believes that in education, entertainment, and industry, devices are already controlled by web pages. In all these cases, device control requires the installation of adapters and drivers.
The serial web API enhances the user experience by allowing direct communication between a website and a device. This is in addition to the WebUSB API, which is supported since Chrome 61, but is not supported by Firefox or Safari for security and privacy reasons. Its original trial version is complete and the Web Serial API is now enabled on the desktop. There is a demo available on GitHub.
Another new feature is that Chrome now supports AVIF content decoding natively using AV1 decoders existing in Android and WebView. (Added desktop support in Chrome 85). AVIF is a next-generation image format standardized by the Alliance for Open Media.
According to the Chromium team, There are three main motivations that led to native AVIF support:
- Reduce bandwidth consumption to load pages faster and reduce overall data consumption. AVIF would offer a significant reduction in image file size compared to JPEG or WebP formats
- The addition of HDR color support. AVIF is a path to HDR image support for the web. In practice, JPEG is limited to 8-bit color depth. With displays increasingly capable of greater brightness, color depth, and gamut, web players are increasingly interested in preserving lost image data with JPEG
- Support the interest of ecosystems. Companies with a strong web presence have expressed an interest in submitting AVIF images to the web.
Of the other changes:
- Full syntax support for "filtering" properties on SVG elements
- Web authentication API: ResidentKeyRequirement and credProps extension
- New CSS features in Chrome 89
- Flux Related Corner Fillet Properties
- Property of forced colors
- Forced color adjustment property
- Delete events with prefix
- Stop cloning session Open windows storage without opening