- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Fri, 11 Oct 2019 14:21:32 +0000
- To: public-web-nfc@w3.org
OK, sorry, so now the pages are gated unless user activation is sensed. Once "we make NFC tap count as a user activation" (by updating the implementation), then the gate is lifted and pages can play sound by reacting to Promise and by watching the event? (from the pov that does the API and spec need to change?) Is there some standard wording that needs to be included for activation?) I assume this could be handled as a policy that is tied to a particular implementation, Android + Chrome in this case, and therefore could be encapsulated in the implementation, just like other UX related policies, so it should not creep up into the spec. Is that correct, or is there a reason for a spec change? (since the issue is filed against the spec). -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/368#issuecomment-541085164 using your GitHub account
Received on Friday, 11 October 2019 14:21:33 UTC