- From: Donna Wu via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Jul 2019 09:44:48 +0000
- To: public-web-nfc@w3.org
DonnaWuDongxia has just created a new issue for https://github.com/w3c/web-nfc: == Should we just ignore the Abort signal and wait for push response for cannot cancel case? == In the SPEC, step 8.2 in the [push method](https://w3c.github.io/web-nfc/#the-push-method): "If the instance has already initiated NFC data transfer, reject p with "NoModificationAllowedError" DOMException and abort these steps." If we fail to cancel the push request, push request may succeed or fail with a different error. If we just reject the promise with a "NoModificationAllowedError" exception, the developer may lose detailed imformation. So shall we just rely on the push response if the the operation cannot be canceled? Actually, for currently case(the NfcImpl.java on Android), if we fail to cancel the push request, the push response will always be called before cancel response. So "NoModificationAllowedError" exception should never occur. Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/239 using your GitHub account
Received on Tuesday, 2 July 2019 09:44:50 UTC