Google announced the availability of Google Chrome 62 Stable today for all supported operating systems on the Chrome Releases blog.
The new version of Chrome brings the version of the web browser to 62.0.3202.62 on the stable channel.
Chrome 62 comes with security fixes and other improvements. Google released the full change log on the Google Source website; beware, the log is very long and it may take hours for you to go through it.
The following guide lists the most important changes of Chrome 62 Stable so that you don't have to check the log yourself.
You may load chrome://settings/help to check the version of the browser, and run an automatic update check. Chrome will download and install the latest version automatically if the version on the local system is outdated.
Google announced earlier this year that it planned to mark HTTP pages as insecure in the browser. Google's plan back then was to mark any HTTP page as insecure in Incognito Mode in Chrome 62, and any HTTP page when entering data into forms as insecure even in the regular browser.
This is not the case apparently, at least not on Windows after the update to Chrome 62. Incognito Mode does not mark HTTP pages as "not secure" for instance. It is unclear if this is going to roll out at a later point in time.
A new about:flags to force the color profile
This option provides you with an experimental flag to enforce a color profile. You can switch from using the default color profile to enforcing sRGB, Display P3 D65, Color spin with gamma 2.4, or scrRGB linear (HDR where available).
The previously available "color correct rendering" flag has been removed as a consequence.
Direct link: chrome://flags/#force-color-profile
A new flag to control sound content
Chrome 62.0 comes with a new Sound content setting to enable site-wide muting in Chrome's content settings and the tab context menu.
Direct link: chrome://flags/#sound-content-setting
New Encrypted Header Extensions for SRTP in WebRTC flag
You may set this flag, or the corresponding Chrome startup parameter, so that WebRTC tries to negotiate encrypted header extensions for SRTP.
Direct link: chrome://flags/#enable-webrtc-srtp-encrypted-headers
New Click to open embedded PDFs flag
This new flag displays a placeholder if Chrome's PDF plugin is not available. It includes an option to open the embedded PDF document in that case.
Direct link: chrome://flags/#click-to-open-pdf
Google announced earlier this week that it will improve Chrome's handling of unwanted software offers and the changes that go along with them that affect the browser. It partnered up with ESET to scan Windows devices for installed software, and prompt users to remove those it classifies as unwanted.
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.