Google Chrome 62 Stable is out
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 Chrome 62 Stable
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.
On to the changes that found their way into Chrome 62
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
- Showing long passwords properly on the password manager settings page.
- Open a windowed settings page rather than open chrome://settings page in
browers when user clicks setting link
- Strengthen the Popunder Preventer.
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.
Google 6 months ago: “We are working to make Chrome less of a resource hog”
Google today: “We are adding a quasi-antivirus program to our browser that promises to use more resources”
Easy, they’re just replacing the downloads scanner engine that was already there.
I hate the scanner. It often blocks unharmful files for no apparent reasons. E.g. regular MP3s.
Resource usage does not concern me much. I run on a 2 year old lower end laptop with more resource than I almost ever need.
So, this update doesn’t bring the new “built-in AV” yet?
The best change is that now, on Linux, Chrome uses native GTK window buttons as it should be. I have the buttons on the left, and now they are nicely integrated with the rest.
Chrome Version 62.0.3202.62 (Official Build) beta (64-bit) under Windows 10 FCU offers Settings – “Font Size” and “Customize Fonts” which can be useful for legibility.
Hi! Where can I find Chrome 62 for Android changes and improvements ?