Re: [web-nfc] Suggest a permission UI flow

We need to make a decision for the upcoming version of the spec. I 
propose what seems to be (close to) the consensus here:

- No prompts required for same-origin access (eventually 
ask-forgiveness).
- User permission required for cross-origin access (including legacy 
tags); if not obtained for any reason (including that the browser 
doesn't want to show user prompts), methods will fail.
- Use Alex' idea for implementation: origin saved in NDEF Id, support 
partitioned writes, but no white list support in the coming version. 
Track white list support in an enhancement issue. Remove Web NFC 
record from the spec (since it's not needed at the moment).
- No permissions required for partitioned writes (since they are 
same-origin by definition).
- Require permission for erase+write (unless same origin).
- Optionally, use paths along with origins, to support watch() 
filtering within same-origin.

-- 
GitHub Notif of comment by zolkis
See https://github.com/w3c/web-nfc/issues/3#issuecomment-132987160

Received on Thursday, 20 August 2015 12:06:40 UTC