A look at Microsoft Edge's new Quiet Notifications system
All modern web browsers support notification APIs that allow sites to push short messages to user devices once the request to accept notifications from that particular site has been accepted by the user.
What has been designed as a way for sites to keep users informed, e.g. of new events, auctions that are running out, new articles or tips, has turned into an Internet-wide overload of notification prompts and notifications; many serve no other purpose than to push advertisement to user systems.
Browser makers started to address issues associated with browser notifications recently. Google introduced quieter notifications in Chrome 80, and Mozilla toned down web notification requests in Firefox 72 as well. The systems have in common that they hide the big request prompts in the browser's user interface when enabled and move it to the browser's address bar instead.
Microsoft added quiet notifications support to its new Microsoft Edge 84 web browser recently as well. The company revealed that it talked to users of its browser to find out more about the real-world use of notifications. It found out that users disliked notification requests, especially when it was not cleared what the site intended to do with the permission and when they did not know anything about the site, but that there were cases in which notifications were used.
Microsoft enabled Quiet notification requests for all users in Microsoft Edge 84, and added an option to the settings to disable the feature. Most users probably want to keep it turned on though as it hides notification prompts on all visited sites in Edge and moves indicators to the Edge toolbar instead.
With quiet requests enabled, site notification requests made via the Notifications or Push APIs will appear as a bell labeled â€œNotifications blockedâ€ in the address bar, as opposed to the typical full flyout prompt.
Edge displays a bell icon in the address bar when a site tries to get permission for sending notifications to the user device; this is the case even when the request was initiated by the user, e.g. by clicking on a bell icon on the site.
A click or tap on the icon displays the prompt, and it is possible to allow or deny it.
The main effect of moving the requests to the address bar is that users are no longer hammered by requests on the Internet. It is possible to do nothing and not be bothered by notification permission requests.
Managing notifications in Microsoft Edge
Edge users may load edge://settings/content/notifications to manage notifications in the browser. The options allow users to block all notifications in the browser, to manage allow and deny lists, and to turn quiet notifications on or off.
- Ask before sending (recommended) -- Enabled by default to allow sites to push requests for notifications to the user. Disable to turn notifications off.
- Quiet notification requests -- Enabled by default to redirect notification prompts to the address bar to avoid user frustration with prompts. Disable to restore the regular notification prompts.
- Block and Allow -- Useful to block certain sites from ever displaying notifications or to allow certain sites to display notifications.
Depending on your use of the Internet, you may not see that many notification prompts or you may be bombarded by them every day. While there are certainly legitimate uses, most sites that implement notifications use them more for advertisement or outright malicious intents.
Now You: Do you make use of notifications on the Internet?Advertisement