Re: [web-nfc] Error event handling should specific the error code (#549)

Obtaining permission is handled by scan(). At the time of reading, the permission is either granted or rejected in the interaction flow. After that, the user should only have the option to either touch a tag or cancel the operation.

Or do you mean that depending on implementation, the permission dialog might be persistent over time during the whole session and a user could deny permission even while making a gesture to touch a tag?

That would be bad UI and it would be quite schizophrenic from a user. What I expect to happen is a race condition in the underlying platform + HW. At that point the read might be successful, but the implementation could still decide to not report the NDEF message (and eventually fire an error event). For this eventuality we could include an extra step in the reading algorithm.

However, this scenario seems invalid to me. As said above, in the Web NFC interaction flow the permission is handled by scan(), and if the user changes opinion, then has the options to not touch a tag and/or cancel the operation.

-- 
GitHub Notification of comment by zolkis
Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/549#issuecomment-597488409 using your GitHub account

Received on Wednesday, 11 March 2020 07:43:04 UTC