Quote:Chrome 72 adds various novelties that the regular user won't notice, including a declaration of public class fields in scripts, a new User Activation Query API, service worker improvements, worker unhandled exception propagation, and other such elements that you can study in this in-depth article.

It also improves interoperability with other major web browsers and deprecates support for the TLS 1.0 and TLS 1.1 security standards, with the removal expected to finish in Chrome 81, due early 2020. It also no longer allows pop-ups during page unload, removes HTTP-based public key pinning, and preps users for the FTP deprecation.

"When even the linux kernel is migrating off of it, it's time to move on. One step toward deprecation and removal is to deprecate rendering resources from FTP servers and instead download them. Chrome will still generate directory listings, but any non-directory listing will be downloaded rather than rendered in the browser," said Google.

With this release, Google fixes no less than 58 security vulnerabilities that affect numerous components of its Chromium-based web browser. Details about the security fixes implemented in Chrome 72 are available in the release announcement, along with the rewards received by the security researchers who discovered them.