I also have it enabled for a website that sends out notifications when they go live for their podcast, the google play music site has them enabled for me to show song titles and album art when the song changes, and Circle-CI has them turned on for when builds pass/fail, but for some reason that one only works when I have the tab open...
That being said, i'm more than happy with this new UI! It's easy enough to find that sites can implement directions for users to go enable it if they want, and it's not in everyone's face for every news site that spams asking for it.
Hopefully, with this browser change, they will.
https://medium.com/the-guardian-mobile-innovation-lab/genera...
It's a pretty fascinating feature set. You can attach images, update the content of an existing notification, attach buttons to perform custom actions, choose to make it silent or not... I think there is more utility than most implementations in the wild would suggest. One fascinating aspect of it for me is that you can do very time limited things (e.g. send election results) - users might be reluctant to download an entire app just for one evening of updates, but being able to send notification through the browser sidesteps that entirely (and more broadly, it puts a useful tool in the hands of people who can't afford native development).
That said, I agree that it's total madness that the default UI allows you to ask for permission on page load. We always had the prompt behind a button on the page and it worked great, so I think Mozilla have the right idea here.
It's actually really irritating the number of random websites that immediately popup an obtrusive notification prompt - I can only guess that they are hoping people accidentally click on the wrong button, and don't know how to disable it...
I know that's not what you're asking for, but it's something to build upon.
I'm building a tool that uses browser notifications to ping when something new is created. It only asks for permission, when a user clicks the button which is clearly labeled to "setup browser notifications". It also sends only 1! notification until the browser tab is opened again, to not spam.
The most annoying are news/blog sites. Who the hell actually clicks Allow? Like 1%? 2%?
That also includes people that just randomly accept any notification their computer gives them. This is older people who don't understand the specific permissions they are granting.
There was one time I was clicking on a navigation element right as a popup for notifications popped up and i accidently clicked it. I immediately went in and reverse the permission to block access, but I am sure there are use cases of accidental acceptance as well.
So considering all of that. My guess is that real intentional adoption is below 1%.
So, the browser vendors worked around this by making it prominent. I think the interface was actually pretty reasonable for these legitimate use cases.
Unfortunately, reasonable tools that capture traffic will always be abused.
A better idea is just to highlight the program in the task bar, as Windows XP did. In this case you can view the messages when it is convenient for you.
I think the use case for legit notifications is very small, thus the UI should be an opt-in, rather than an intrusive pop-up.
I never understood why browser makers gave it such a prominent UI, and of course in this attention seeking market it was bound to be abused. The new UI that Firefox is suggesting in the article is good, this should have been like this from the first day. I hope other browser vendors quickly follow.