Chrome to follow Firefox, stifle site notification appeals in version 80

Google said yesterday that within four weeks, Chrome would follow Firefox's lead and tamper with hateful websites' requests for users to tinker with notifications.

"As a useful service to protect Internet Service notifications ... Chrome 80૦ will show, under certain conditions, a new, quieter notification permission UI [user interface] that reduces the interruption of notification permission requests [sic]," wrote one Google product manager.

What Firefox is doing

Mozilla, the creator of Firefox, just rolled out 72 versions this week. High on the list of new features for the browser: the end of intrusive, page-blurred pop-ups from sites that ask users to send future notifications.

Firefox 72 will prevent most of these pop-ups from appearing. Instead, the browser will display a small cartoon speech bubble in the address bar, then jiggle it briefly for attention. The user can ignore it - leaving the bubble in place - or interact with it later to show pop-ups and choose whether to accept notifications from the site.

Mozilla's complaint about the site notification appeal is silent on two facts. First, the vast majority of requests are rejected - ultimately, 99%, according to Perm's research - and second, pop-ups interrupt the user's workflow.

Chrome has a similar problem

Google set a more compromising tone. Calling notifications a "necessary capability" for some web applications, McLachlan also said that Google intended to "protect notifications as a useful service for users."
Chrome 80 treats site requests in the same way as Firefox to२. Instead of allowing pages that ask for permission to send pop-ups to sites, Chrome Google કહે calls Google a "silent UI", with a single alarm bell sliding across the icon. By strike. Desktop .For Chrome, the icon will appear near the right edge of the address bar. (On mobile Chrome, it will appear near the bottom of the screen.) Chrome first introduces a quiet UI, an in-browser dialog that can be fired, explaining the feature.
Users will be able to manually add a new notification request UI using the new option found in Settings> Advanced> Privacy and security> Site settings> Notifications. Turning on "Use silent messaging (blocking instructions instructs you to interrupt) turns on a pop-up blocker."

Google will automatically enable silent UI for some users. People who "frequently decline" notification requests will be auto-registered, McLachlan said without explanation. Google will also automatically silence some sites.

"Sites with very low acceptance rates will be automatically registered at silent prompts," McLachlan added. "Once the user experience is improved they will be automatically enrolled."

McLachlan criticized sites that promptly request permission, saying that acceptance rates on those websites are often very low. "We recommend that users wait for websites to understand the context and see the benefit of receiving notifications before asking permission," he wrote.

Google has repeatedly used Chrome to force websites to make changes that the search giant believes are generally beneficial to the web. An example of this is Google's push to get sites to adopt HTTP. Mountain View, Calif. The company will use the same tactic here on notification appeals - on company notification appeals, penalizing sites that do not meet its guidelines. Chrome can dominate the browser market because of Chrome: In December, 66 66..6% of all personal computer browser activity was deployed to Chrome, overwhelming any competitor (the nearest competitor was Firefox, with palletry.4.4%. Was).

Firefox's approach did not bother trying to impress websites for their simple instruction that Mozilla and its small browser would make a few changes under the threat of share. Chrome.