Google Chrome 60.0.3112.78: Google last night promoted the program tours Chrome on the stable channel for all supported platforms (Windows, macOS and GNU/Linux) adding many security fixes and various improvements.
Earlier yesterday he launched the beta version, but a few hours later, the Google Chrome 60.0.3112.78 update was placed on the fixed channel and is now the latest stable version of the popular browser. 
As for the important improvements implemented by Google in this update, we can mention that the Payment Request API is now supported, on the Android platform, it is now possible to use VP9 of a video encoding format with MP4 (ISO BMFF) container, and a new VP9 string format format.
Starting with Chrome 60, Google has excluded the use of custom fetch () to access saved passwords in an attempt to make Credential Management API easier to use for developers. In addition, Chrome now supports the CSS @ font-face descriptor, the CSS font-display property, and a new Paint Timing API.
The new Google Chrome 60 also fixes total 40 security issues, including use after free bugs in IndexedDB, V8, and PPAPI, a spoofing UI in the Blink engine, a type of confusion in the extensions, an out-of-bounds write issues in PDFium andPPAPI , leaks in Android user data, and an out-of-bounds read in Skia.
It also fixes three URL spoofing bugs in OmniBox, a use after free in Chrome Apps, an unauthorized use of Skia, a spoofing UI in the browser, a SQLite pointer revelation, SVG user information leak, UI spoofing in the payment window and another UI spoofing in the browser.
More details about these security fixes you can find in the release release and you can download the new Google Chrome 60.0.3112.78 from the link below.
https://www.google.com/chrome/
