- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Aug 2015 20:52:15 +0000
- To: public-web-nfc@w3.org
> I'd favor an nfc.watch(...) function that takes options about how the watch should proceed, and asks the UA to fire 'message' events when a matching NFC device is found. I agree that having a watch() function instead of using addEventListener would be semantically more correct, especially for handling security dialogs and then optionally handle filters/constraints. We used to have that function in earlier versions of the spec, but it seems we have oversimplified things and now have bumped into its price. The current send() function is also semantically misleading, as in fact it means setting a message which will be sent when the proximity range is reached (an asynchronous operation with timeout). > @sicking has a good point in #3 That is fine with me too. > Spec-wise, the "User agents must implement the following policies" section doesn't work as-is: these restrictions need to be in the algorithms they apply to, in which place they can say what to do when the user hasn't given permission. Ok, I will move them into algorithms. -- GitHub Notif of comment by zolkis See https://github.com/w3c/web-nfc/issues/40#issuecomment-132347307
Received on Tuesday, 18 August 2015 20:52:17 UTC