- From: François Beaufort via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 Dec 2020 13:39:18 +0000
- To: public-web-nfc@w3.org
In example below, how do we know that ndef1 is not listening anymore? Or is this what we want?
```js
const ndef1 = new NDEFReader();
await ndef1.scan(); // Promise resolves and reading occurs...
ndef1.onreading => ({message}) => { /* Handle NDEF message */}
// few seconds later
const ndef2 = new NDEFReader();
await ndef2.scan(); // Promise resolves and reading occurs
ndef2.onreading => ({message}) => { /* Handle NDEF message */}
// ndef2 will get reading events.
// How about ndef1?
```
--
GitHub Notification of comment by beaufortfrancois
Please view or discuss this issue at https://github.com/w3c/web-nfc/pull/611#issuecomment-745292309 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 15 December 2020 13:39:19 UTC