Chrome 84 release: block intrusive notification requests


Following the release of version 83 on Android, Mac, Windows and Linux, the next version of the Google browser will be released. Chrome 84 introduces a handful of user-oriented changes and new capabilities for web developers.

After falling behind due to COVID-19 and not wanting to negatively impact banking, supermarkets, government, and other essential service sites, SameSite cookie tagging it will be gradually redeployed in version 84. This secure handling of third-party cookies by default limits tracking and increases privacy.

Abusive notification notifications are “one of the main complaints from users”. Chrome 84 is addressing this by blocking intrusive notifications and other site permission requests that repeatedly annoy users about enabling. Based on version 80’s quieter notification user interface, the goal is to discourage users from giving sites the ability to display alerts.

Google has been working to reduce CPU and power consumption in recent releases. Chrome will detect when a the browser window is covered on the other to suspend work by painting pixels, thus preserving resources when a page is not being viewed. This feature will appear for some users in version 84, and a broader version is expected with Chrome 85. It is based on Chrome freeze tabs, except for playing audio / video and recording, which have been in the background for more than five minutes.

After an extension changes the default search engine or New Tab page, Chrome will confirm the decision with users. If this was done in a dire way, there will be an option to go back to the previous settings.

Chrome 84 adds support for the OTP web (one-time password) API where the browser will automatically enter the 2FA code sent by SMS to your default messaging application. The browser will slide a panel up so that you “Allow” the code to complete automatically. It is up to individual websites to support this capability.