- From: François Beaufort via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Sep 2020 09:51:50 +0000
- To: public-web-nfc@w3.org
> > Let's keep onerror. What do you folks think? > > So that error could have happened with the write(), too. > When does that error come up typically? Can we handle that via the scan() and write() promise? scan will succeed when scan has started successfully, but this error could happen way after. re: write, it won't be an issue as if this error happens, the promise will reject right away, and the onerror event will also get fired. > > "NDEFReader::OnMojoConnectionError()" is not per-say a reading error but an internal communication issue that can happen in Chromium. > > Do I read that correctly: it seems to reject the promise with that error and _also_ fire an `onerror`? Is the latter needed? > Edit: it's covering the case the error comes _after_ the promise is settled. But does that actually (typically) happen? it is an internal issue which "shouldn't" happen but can happen. -- GitHub Notification of comment by beaufortfrancois Please view or discuss this issue at https://github.com/w3c/web-nfc/pull/601#issuecomment-699904383 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 September 2020 09:51:51 UTC