- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 Sep 2019 19:08:21 +0000
- To: public-web-nfc@w3.org
@kenchris could you help having a second eye on the scan algorithm for this case: 1. `scan()` is invoked with `options` that contain a `signal`: the internal slots get initialized, content is listened for. 2. `scan()` is invoked again, with different `options` that _do not_ contain a `signal`. The rest of `options` replaces the internal slots, but what happens to the abort signal? Will the previously set value stay (yes, if I read the algo correctly) and is that something we want? -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/351#issuecomment-531915436 using your GitHub account
Received on Monday, 16 September 2019 19:08:36 UTC