- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Dec 2020 09:58:52 +0000
- To: public-web-nfc@w3.org
@beaufortfrancois Does it mean we deliberately make scan behavior different from write behavior? Writes cancel previous writes. It seems you proposing the opposite for reads, i.e. that new scans should not replace previous scans, but fail with the error? We seem to have implementation for this, whether or not it is the correct, or desired behavior. But this would prevent the issue of how to notify about stopping event delivery for ongoing scans (we don't have a notification implemented yet). Although we could use the `onreadingerror` event to notify about scans being aborted (for any reason). In my view, both are doable, we need to select one with good reasoning and we need to explain in a note why. Please suggest a text for that. About multiple reads, the API design with read events works with both single and multiple reads, regardless of what the implementation supports, which is a good thing. -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/592#issuecomment-746014634 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 December 2020 09:58:54 UTC