Google always accompany Chrome updates with release notes aimed at highlighting the upcoming changes, additions, enhancements and modifications, especially for enterprises that are planned for the browser.

While Chrome has continued to dominate the browser market, with about 69% of the world's user share, which is calculated as a measure of monthly browser activity by Net Applications. Google's browser, Chrome has eclipsed even the closest rivals like Firefox, with Mozilla now fighting for left overs, and the erstwhile browser leader, Microsoft haven adopted Chromium technology to align with Google in order to still remain relevant.

Chrome is currently used same way that Microsoft's Internet Explorer (IE) 6 was back in the days, where developers primarily optimize their web contents for Chrome, leaving out later tweaking for rivals.

Google is the undisputed champion of modern web standards, and in its effort to make the web standards to work across the different browsers, have led the industry effort to modernize the web, and that effort is what has enabled Google to advance its services like Gmail, G Suite (formerly, Google Apps) and other productivity tools.

What's coming in next versions of Chrome?



Google promised to launch a baked-in hacked-password alert system in Chrome, that will automatically alert users whose details have been compromised, which feature may be similar to the Firefox Monitor which functions more like Troy Hunt’s "Have I Been Pwned", allowing users to search for login details on the service to see if the details are released in a data breach.

The Chrome build that leads to Stable, Chrome 78 Beta, also the less-reliable Chrome 79 Canary for Windows and macOS, already sports the new password checker system, though hidden behind a setting in the options menu.



Google has joined the DNS-over-HTTPS (DoH) bandwagon, which protocol is hyped as a new way to secure communications between DNS (Domain Name Service) server and the browser. The company has announced plans to implement DNS-over-HTTPS (DoH) in the next version of its browser, Chrome 78 with option of choosing the corresponding DoH server to use for DNS resolution.

This is coming on the heels of Mozilla's already running support for DoH in the main Firefox release for a small percentage of its users, and promise of making it available for all users. While the support for DoH started with Firefox 62 to improve the way the browser interacts with DNS, using encrypted networking to obtain DNS information from the server.

Starting with Chrome 79, Google will commence the trial for DoH, whereby DNS requests from users will automatically be switched to pre-selected DNS provider's DoH service if available.



Google has also laid out plans to deprecate legacy versions of the Transport Layer Security (TLS) 1.0 and 1.1 cryptographic protocol that is used to encrypt communications between the browsers and website servers. Beginning from Jan. 13, 2020, Chrome 79 will start displaying "Your connection to this site is not fully secure" whenever a user connects to a site running the outdated protocols.

Google will equally stop supporting FTP (File Transfer Protocol) which is an outdated protocol that transfers files over unencrypted connection, starting with Chrome 80 and recommends that IT administrators should move to native FTP clients instead.

What's new in the latest Chrome update & Google's plans for the future



Google always accompany Chrome updates with release notes aimed at highlighting the upcoming changes, additions, enhancements and modifications, especially for enterprises that are planned for the browser.

While Chrome has continued to dominate the browser market, with about 69% of the world's user share, which is calculated as a measure of monthly browser activity by Net Applications. Google's browser, Chrome has eclipsed even the closest rivals like Firefox, with Mozilla now fighting for left overs, and the erstwhile browser leader, Microsoft haven adopted Chromium technology to align with Google in order to still remain relevant.

Chrome is currently used same way that Microsoft's Internet Explorer (IE) 6 was back in the days, where developers primarily optimize their web contents for Chrome, leaving out later tweaking for rivals.

Google is the undisputed champion of modern web standards, and in its effort to make the web standards to work across the different browsers, have led the industry effort to modernize the web, and that effort is what has enabled Google to advance its services like Gmail, G Suite (formerly, Google Apps) and other productivity tools.

What's coming in next versions of Chrome?



Google promised to launch a baked-in hacked-password alert system in Chrome, that will automatically alert users whose details have been compromised, which feature may be similar to the Firefox Monitor which functions more like Troy Hunt’s "Have I Been Pwned", allowing users to search for login details on the service to see if the details are released in a data breach.

The Chrome build that leads to Stable, Chrome 78 Beta, also the less-reliable Chrome 79 Canary for Windows and macOS, already sports the new password checker system, though hidden behind a setting in the options menu.



Google has joined the DNS-over-HTTPS (DoH) bandwagon, which protocol is hyped as a new way to secure communications between DNS (Domain Name Service) server and the browser. The company has announced plans to implement DNS-over-HTTPS (DoH) in the next version of its browser, Chrome 78 with option of choosing the corresponding DoH server to use for DNS resolution.

This is coming on the heels of Mozilla's already running support for DoH in the main Firefox release for a small percentage of its users, and promise of making it available for all users. While the support for DoH started with Firefox 62 to improve the way the browser interacts with DNS, using encrypted networking to obtain DNS information from the server.

Starting with Chrome 79, Google will commence the trial for DoH, whereby DNS requests from users will automatically be switched to pre-selected DNS provider's DoH service if available.



Google has also laid out plans to deprecate legacy versions of the Transport Layer Security (TLS) 1.0 and 1.1 cryptographic protocol that is used to encrypt communications between the browsers and website servers. Beginning from Jan. 13, 2020, Chrome 79 will start displaying "Your connection to this site is not fully secure" whenever a user connects to a site running the outdated protocols.

Google will equally stop supporting FTP (File Transfer Protocol) which is an outdated protocol that transfers files over unencrypted connection, starting with Chrome 80 and recommends that IT administrators should move to native FTP clients instead.

No comments