- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Sat, 29 Sep 2018 11:06:11 +0000
- To: public-web-nfc@w3.org
> Does creating it have to be async? Your last IDL block has it as promise-returning, and it's not clear to me why. The [watch()](https://w3c.github.io/web-nfc/#dom-nfc-watch) algorithm was asynchronous, but indeed the user intent to create a read filter does not need to wait until NFC is configured, so we could create the object right away. We could handle security/permissions/support errors with exceptions. We could eventually include an `onerror` event on the `NFCReadFilter` object to report NFC/read errors. -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/152#issuecomment-425636761 using your GitHub account
Received on Saturday, 29 September 2018 11:06:17 UTC