Browse the web both regularly or in private mode, open as many as tabs as you want, watch videos from YouTube and other websites without installing Adobe's Flash player, bookmark your favorite websites and save login credentials for various websites.
Still considered the world’s favorite browser, Google Chrome does not cease to amaze its millions of users with every new version while attracting new ones at the same time. Being a Google product, Chrome syncs perfectly with all your Google accounts and products, allowing you to access all your data virtually from anywhere. Its privacy and accessibility features are also among the best available out there.
Taking into account that both Opera and the new Microsoft Edge are both based on Google’s Chromium technology, it is safe to say that it has proven to be the fastest and most reliable Web browsing technology you can use. The devil is, as usual, in the detail. The technology behind them may be exactly the same, but both in terms of browser design and resource management, there are big differences among all Chromium-based browsers.
For obvious reasons, Chrome beats all of them when it comes to Google integration, and this platitude is of a great importance when we ask ourselves this question – who is not connected to Google in one way or another? Therefore, having your browser synchronized with your e-mail account and all your cloud-based data in a simple, transparent, and straightforward way is of great relevance to many users. Hence its growing popularity.
The new version of Google Chrome hasn’t changed significantly neither visually nor functionally when compared to previous ones. And that is both good and bad. Good because regular Chrome users will be glad to find the privacy and security features they all know and love, as well as the Incognito browsing mode, the myriad of extensions available and, of course, the Google search engine in all its glory. And bad because this browser still has the dubious honor of being (also) the leader among all resource-hungry browsers. And this is not a Chromium-related issue, as other Chromium-based browsers display a clearly better resource management policy.
Google Chrome hasn’t stopped topping the charts of the “Best Browser of the Year” lists during the last few years, but other contenders are getting closer, especially in terms of memory management. If ever this browser manages to sort out this issue, no other contender will dare to dispute its domination.
v80.0 [Nov 12, 2019]
- Updates to cookies with SameSite: Starting in Chrome 80, cookies that don’t specify a SameSite attribute will be treated as if they were SameSite=Lax. Cookies that still need to be delivered in a cross-site context can explicitly request SameSite=None. Cookies with SameSite=None must also be marked Secure and delivered over HTTPS. To reduce disruption, the updates will be enabled gradually, so different users will see it at different times. We recommend that you test critical sites using the instructions for testing.
- Pop-ups and synchronous XHR requests not allowed on page unload: Pop-ups and synchronous XHR requests won’t be allowed on page unload. This change will improve page load time and make code paths simpler and more reliable. If you encounter incompatibilities with legacy software, you will be able to revert to behavior matching Chrome 79 and earlier using the following policies, which will be available until Chrome 88:
- To allow pop-ups on page unload, see AllowPopupsDuringPageUnload.
- To allow synchronous XHRs on page unload, see AllowSyncXHRInPageDismissal.
- Control data types in Chrome sync: Chrome users have the ability to granularly enable or disable each type of data that’s synchronized in the advanced Data from Chrome sync settings. In Chrome 80, you can also control the data types synced using the SyncTypesListDisabled policy.
- Changes to how HTTPS pages load secure subresources in Chrome 80 and 81: In Chrome 80, http:// audio and video resources on https:// pages will be autoupgraded to https://, and Chrome will block them by default if they fail to load over https://. Users can unblock affected audio and video resources by clicking on the lock icon on the address bar and selecting Site Settings. In Chrome 80, http:// images on https:// pages will still be allowed to load, but users will see “Not Secure” on the address bar. In Chrome 81, http:// images on https:// pages will be autoupgraded to https://, and Chrome will block them by default if they fail to load over https://. You can control these changes using the StricterMixedContentTreatmentEnabled policy, which disables autoupgrades for audio and video and the warning for images. This policy is a temporary policy and will be removed in Chrome 84. The InsecureContentAllowedForUrls and InsecureContentBlockedForUrls policies will control the site setting described above. You should begin ensuring that resources in pages are fetched over HTTPS and manage exceptions using a policy. For more information, see the Chromium blog.
- Control if websites can check for user payment methods: The PaymentMethodQueryEnabled policy allows you to control if websites can check for user payment methods. For details, see PaymentMethodQueryEnabled.
- Web Components v0 removed: The Web Components v0 APIs (Shadow DOM v0, Custom Elements v0, and HTML Imports) were supported only by Chrome Browser. To ensure interoperability with other browsers, late last year, we announced that these v0 APIs were deprecated and will be removed in Chrome 80. For more information, see the Web Components update. Until Chrome 85, you can use the WebComponentsV0Enabled policy to re-enable web components v0.
- Introduction of tab groups for some users: Starting in Chrome 80, some users will be able to organize their tabs by grouping them on the tab strip. Each group can have a color and a name to help your users keep track of their different tasks and workflows. A wider rollout is planned for Chrome 81.
- Block external extensions: In Chrome 80, you can use the BlockExternalExtensions policy to stop the installation of external extensions on your devices. The policy will not block kiosk apps or extensions installed by policy.
- Chrome Browser Cloud Management Reporting Companion no longer required: The functionality previously provided by the Chrome Browser Cloud Management - Reporting Companion extension has been integrated directly into Chrome Browser. If you’re using Chrome Browser Cloud Management, users will no longer see the extension on their devices when reporting is turned on. No action is required from admins or users.
Mall Creeps
