Notification permission requirement

[mkruisselbrink]

Notification permission requirement

[mkruisselbrink]

For an API like this (which might be called in contexts where permission prompts can't be shown like service workers, or without user interaction) generally the user agent automatically showing a permission prompt doesn't work very well. Although it is one thing I am considering maybe doing. It would at least be better than user agent sniffing or unconditionally requesting permission...

[mkruisselbrink]

It's a requirement in Safari, and it might become a requirement in Chrome on MacOS (for the same OS reasons that it is a requirement in Safari I imagine).

[fallaciousreasoning]

I think if the user agent wants, they can show the required permission prompt when the app tries to set a badge, so websites shouldn't need to worry about requesting the permission separately. Was that what we intended here @marcoscaceres? Sounds like it might be worth cleaning up anyway

[tomayac]

unconditionally requesting permission...

This is what the demo does now unfortunately.

[fallaciousreasoning]

Good point @mkruisselbrink - I've clearly been out of it for a while 😆

Hmm, definitely feels unideal that the demo is unconditionally requesting permission to show notifications - Is it a requirement now, that the notifications permission is granted?