Every four weeks, Google releases a new version of Chrome to the stable channel. However, it is changing its release cadence slightly with Chrome 110. Instead of releasing Chrome 110 to stable four weeks after Chrome 109, it’s rolling out the latest version a week earlier on a new “early stable” channel. This means that Chrome 110 will arrive in Early Stable today, three weeks after the release of Chrome 109, and Stable next week. As mentioned on Chromium Dash..
Releasing today, Google Chrome 110 packs a very long changelog. Although Chrome 109 was considered the first version of the browser to implement Google’s third-party cookie replacement. Cookies containing independent distributed state (CHIPS).it has apparently been pushed to Chrome 110 instead.
Moreover Opt-out mechanism for secure payment verification Allowing users to remove their information from the developer’s server has also been implemented. And while the details are too technical for most of us, external HTTPS server implementers may also want to take a look. TLS client hello extension configuration which ensures that the protocol is more robust to changes.
Also, there is More access control around the navigator.share() function With capability for third-party iframes objects Load new documents into them using context less than temporary credentials.And Web apps can also customize their launch behavior. Based on different motivations. Similarly, Cross-origin iframe support has been added for the FedCM API.is defined by web developers and browser vendors (Apple, Mozilla) alike.
Another important change is this. Chrome allows 110 deviant characters. Like “ß” and “ς” in domain names, just like Firefox and Safari – both of which have been handling them correctly since 2016. Some other changes that are commonly available are listed below:
This release of Chrome includes many features currently in developer and origin trials, you can see a summary of them below:
- Developer trial (behind the flag)
- The original trial
Finally, some are accompanied by depreciation and removal. Completely deprecating WebSQL in non-secure contexts. After deprecation in Chrome 105. Similarly, The legacy storage quota API “window.webkitStorageInfo” is being removed.. It has been deprecated since 2013 and the removal is expected to have little impact as no other browsers implement it.
It’s important to note that while Chrome is hitting 110 Early Stable today, there is no opt-in mechanism. The update will be rolled out to a “small percentage of users” based on some undisclosed criteria and the idea is to identify any critical issues before the actual stable release on February 7th. .
