- From: François Beaufort via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Sep 2020 07:59:49 +0000
- To: public-web-nfc@w3.org
Argh I see now... You're right @arskama, the first one "NDEFReader::OnMojoConnectionError()" is not per-say a reading error but an internal communication issue that can happen in Chromium. If I remember correctly though, there's no way to recover from this. The old behaviour still triggered an error even though it was NOT specifically a reading error. With that in mind, maybe keeping `onerror` makes sense. For info, this will also get triggered if an internal error happens during a write NFC operation and `write()` promise will reject as well... Let's keep `onerror`. What do you folks think? -- GitHub Notification of comment by beaufortfrancois Please view or discuss this issue at https://github.com/w3c/web-nfc/pull/601#issuecomment-699846984 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 07:59:51 UTC