- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Oct 2015 12:35:02 +0000
- To: public-web-nfc@w3.org
If adapter is changed to a second one, we have the following options: 1. [suspend](https://w3c.github.io/web-nfc/index.html#steps-focus-lost) the first adapter 2. [release](https://w3c.github.io/web-nfc/index.html#releasing-nfcadapter) the first adapter 3. reject if this is not the first invocation of requestAdapter() (or requestNFC). I see more problems/inconsistencies with policy 3 than either with policy 1 or 2. In addition, we discussed with @alexshalamov that a non-fingerprintable id (like "nfc1", "nfc2" etc) could be included to an NFCAdapter, in order that clients could tell them apart. -- GitHub Notif of comment by zolkis See https://github.com/w3c/web-nfc/issues/67#issuecomment-150559598
Received on Friday, 23 October 2015 12:35:07 UTC