This is fantastic! I had finally figured out I could turn this off in settings a while ago, glad it's now a default. I get so annoyed by this, annoying indeed!
This is fantastic! I had finally figured out I could turn this off in settings a while ago, glad it's now a default. I get so annoyed by this, annoying indeed!
In a webapp where you present user a button to activate notifiactions, when the user clicks the button seemingly nothing happens in FF72 (user is focussed on a big enable notifiactions button in the web app and may not notice that some tiny gray icon wiggled a little in the address bar).
On a big screen a button in the middle of the screen is so far away from the address bar, that you don't see any change in the address bar at all in the peripheral vision.
So yeah, web apps that don't try to force the user to enable notifications are now punished for good behavior again.
EDIT: So it's not so stupid, see below.
This will just not work anymore. I'll have to add some long winded FF specific explanation on what to do after clicking the button.
Anyway the FF UI is broken if user physically can't see any reaction from the browser after he requests notifications by clicking anywhere on the page.
https://hacks.mozilla.org/2019/11/upcoming-notification-perm...
This is a frequent "mistake"/issue however, and we're working on a mitigation for it.
https://megous.com/dl/tmp/sub.txt
I guess this is then happening because I'm first checking if there's a subscription via `pushManager.getSubscription` before creating a new one in the event handler.
Yep, dropping getSubscription makes the popup appear again.
Do you mind me asking what your notifications are for?