- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 May 2019 12:15:39 +0000
- To: public-web-nfc@w3.org
I am fine with keeping it explicit, especially if it has been considered and feedbacked earlier - but I wanted to understand. OK, so when tag comms does not work, we throw an error, so the devs would know it's non-standard. But this could be done even without NDEFCompatibility. What I am trying to understand is whether are you trying to minimize the chance of error reporting by making the devs aware of the compatibility issues and by pushing them to make an explicit choice there? (whereas my thinking was devs would not really care until an error is received, but even then there is not much to do about it than just ack the error, since the platform can't handle it anyway). -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/160#issuecomment-496911194 using your GitHub account
Received on Wednesday, 29 May 2019 12:15:40 UTC