Chrome 77 update with new performance metrics, native lazy loading and more
The Chrome 77 update is now available for Windows, Mac, Linux, Android and iOS. Google is also aiming to improve the performance of its Internet browsers with the new Chrome 77 update. New performance metrics, form capabilities, and key tests now
Google Chrome version 77 is now available for download on Windows, Mac, Linux, Android and iOS. The latest version of Google’s browser includes a number of new features, including new performance metrics, form capabilities, and the Origin Trial. As expected, there are a number of bug fixes, 52 security fixes that need to be corrected, and some fixes that are contributed by external researchers are listed in Google’s blog post. Most of the new features that come with the update are aimed at web developers, but one UI-related change in the browser includes the removal of the UI indicator for Extended Validation (EV) certificates.
Google is also aiming to improve the performance of its Internet browsers with the new Chrome 77 update. In Chrome’s Developer Tools section, there’s a new option called “Largest Contentful Paint” that can be used to measure Chrome’s time to display a readable version of a website in the user-visible section of the browser, with the rest of the site still loading in the background. As someone assumes, this option will enable and optimize the components that should ideally be loaded first, rather than content that is not immediately visible on the screen.
As part of Google’s Origin trial, a new IO component is a new Contact Picker API that can use websites to access and select contacts from a user’s phone. For those who don’t know, Origin Trial is Google’s new approach to enabling experimentation with web platform features in a secure way. It has a dashboard that enables users to sign up for experimental features. In addition, system administrators can now implement and enforce configuration in the Chrome browser across an enterprise. This new feature is called “BrowserGuestModeEnforced”