Last month, Google launched the stable version of Chrome 94. As a result, it caused some controversy due to the introduction of idle detection API and virtual keyboard API. According to the update release cycle reduced from 6 weeks to 4 weeks, the search giant will soon push Chrome 95 to users around the world. These include the latest changes, including the enforced cookie size limit and the removal of support for the FTP file transfer protocol.
It is reported that Chrome 95 has strictly limited the size of cookie name + value to a maximum of 4096 bytes. The length of each attribute is at most 1024 bytes, and the overlength part will be completely rejected. Earlier, Chrome imposed a limit of 4096 bytes for the entire Set-Cookie line. The recent changes can be considered consistent with Mozilla Firefox and improve interoperability. Secondly, Chrome 95 enhanced the user agent (UA) client prompt to cater to the detection of different Windows versions.
The current implementation considers the major and minor versions of Windows components, but they have not changed at all in different Windows 10 (or even Windows 11) versions. Looking to the future, Windows.Foundation.UniversalApiContract will be used to derive which version of Windows and Chrome users are running on. More importantly, Chrome 95 also canceled support for the FTP file transfer protocol. Careful users should find that Chrome no longer supports encrypted FTP connections such as FTPS, and lacks corresponding proxy support.
However, considering that there are more useful FTP clients on the market, the actual user base who needs the FTP function in Chrome is not large. Therefore, Google feels that the complete removal of FTP support will improve the security of the browser. Similarly, Chrome 95 has dropped the uniform resource locator (URL) support for non-IPv4 hostnames (ending in numbers). Although there are no known exploits, Google still regards it as a preventive security measure. The URL specification was also updated to indicate this change. (It is said that only 0.0003% of hostnames are affected).
Join RealMi Central on Telegram, Facebook & Twitter
Then there is the EyeDropper API that has been introduced, which allows websites such as PowerPoint Online to integrate the color picker provided by the browser in their custom color picker. In addition, there is system-level note-taking web application integration. Chrome 95 will be able to parse Web App URL list entries, the payment verification mechanism has also been enhanced, and safe payment measures have been introduced.
There is also the upcoming Web API called URLPattern, which provides native support for URL matching for pattern strings. Previously, this was handled by custom solutions such as JavaScript libraries. The logical properties that are being added that contain internal sizes allow easier code writing in shorthand, and can now be better encapsulated through the custom counter style of the shadow tree. Finally, self.reportError() is a function that allows web developers to report global exceptions to the console to better control custom callbacks. WebAssembly cross-source module sharing is also being deprecated.
Related news also includes the exception handling of WebAssembly, which has received generally positive feedback from web developers and the teams behind Firefox, Edge and Safari. And for developers who use PerformanceObserver, a new dropEntriesCount property has been added to enable them to know how many entries were dropped due to the buffer size exceeded. Interested friends can receive Chrome 95 updates in the near future.
If you can’t wait, you can also click the menu button in the upper right corner, and then move to “Help -> About Google Chrome” to manually check for updates. According to the plan, Chrome 96, which is currently out of the Dev channel, is expected to usher in a stable version on November 16.