- From: Mustaq Ahmed via GitHub <sysbot+gh@w3.org>
- Date: Thu, 31 Oct 2019 15:51:47 +0000
- To: public-web-nfc@w3.org
Yes, "should be gated by user activation" is the right solution, addresses the concerns I had with #368. Re fixing this spec issue: if the plan is to fix this before the user activation PR lands (hopefully in a few weeks), please use "triggered by user activation" for now and cc me in a new issue to rephrase it. Or you can wait. IFAIK Chrome's permission dialog is gated by user activation, at least for the cases I checked. So the chain "NFC gated by permissions gated by user activation" makes perfect sense to me. I am assuming there is no "piece" of the NFC API that does _not_ need a permission yet should be gated by user activation. As a side note, I see that the [Permissions API](https://w3c.github.io/permissions/) does not specify the dependence on user activation. @jyasskin, does it have an issue to cover this? -- GitHub Notification of comment by mustaqahmed Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/425#issuecomment-548441813 using your GitHub account
Received on Thursday, 31 October 2019 15:51:49 UTC