- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Apr 2023 07:23:07 +0000
- To: public-web-nfc@w3.org
> This is actually not needed and can be exercised with the JavaScript code below. Sorry for the noise. > // Waiting for user to tap NFC tag to write to it... > // Now scanning for 3 seconds... > // Scanning is now stopped. So from the user perspective, the tag is just being held there for 3 seconds (or less, until read), and that solves the original issue, that a user was assumed to need to tap, lift, and tap again? But would the second part still make sense for convenience? IIRC we used to have this: what was the reason for removing? Occam, or something more? > I was thinking we could perform a read NFC operation after a write NFC operation and return the NDEFMessage when the NDEFReader.write() promise resolves if web developers expressed it via an NDEFWriteOptions option. -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/654#issuecomment-1524958664 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 April 2023 07:23:09 UTC