[w3c/push-api] Clarify when a site is allowed to display the permission prompt (#328)

In the last years different browsers have introduced [arbitrary limitations](https://blog.pushpad.xyz/2020/10/the-notification-prompt-can-only-be-triggered-by-a-user-gesture-on-some-browsers/) on when the permission prompt can be triggered. Some browsers like Chrome are also introducing [penalties](https://blog.pushpad.xyz/2020/07/chrome-blocks-the-notifications-on-abusive-websites/) for websites that don't follow the rules.

However **the rules are not always clear** and I think that the standard should clarify when a website is allowed to display the permission prompt for notifications. Indeed, whenever we want to try a new way to present the prompt, we always fear the a browser may block that or you can even get penalizations.

For example, I see that there is a trend of **displaying the browser permission prompt directly** (not [a double opt-in](https://blog.pushpad.xyz/2020/04/the-double-opt-in-for-web-push-notifications/]) **after some page scrolling**. Is that an allowed use case or should be avoided? 

This is just one of the doubts that all these limitation and penalties introduce... In order to get peace of mind and compatibility between browsers, I think that the standard should clarify when you can display the prompt.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/328