- From: Marcos Cáceres <notifications@github.com>
- Date: Mon, 08 Aug 2022 18:43:06 -0700
- To: w3c/push-api <push-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 9 August 2022 01:43:18 UTC
Hi @collimarco! > Please clarify in the standard that a browser MUST display the permission prompt after an explicit user interaction (e.g. click on a button). The spec states that: > [User agents](https://w3c.github.io/push-api/#dfn-user-agent) MUST acquire consent for permission through a user interface for each call to the subscribe() method, unless a previous permission grant has been persisted, or a prearranged trust relationship applies. And, in `subscribe()`'s method definition: > "..invoked MUST run the following steps:..."Let permission be [request permission to use](https://www.w3.org/TR/permissions/#dfn-request-permission-to-use) "push". So, it seems you are describing a browser bug, not a spec bug. That spec makes it pretty clear what MUST happen, but for whatever reason, Chrome mobile has chosen a different approach. My recommendations would be to file a bug on Chrome instead? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/push-api/issues/356#issuecomment-1208812950 You are receiving this because you are subscribed to this thread. Message ID: <w3c/push-api/issues/356/1208812950@github.com>
Received on Tuesday, 9 August 2022 01:43:18 UTC