- From: François Beaufort via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Oct 2019 09:28:27 +0000
- To: public-web-nfc@w3.org
beaufortfrancois has just created a new issue for https://github.com/w3c/web-nfc: == Why returning null in arrayBuffer() from text, URL, and external record type? == Spec currently says for `arrayBuffer()`: > 1. If the recordType value is equal to "json" or "opaque", then return an ArrayBuffer whose contents are the bytes. Re-throw any exceptions. > 2. Otherwise, return null. I'm not sure to understand why we should return `null` for text, url, and external record types. I think `arrayBuffer()`should alway return raw bytes and let web developers handle those. Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/371 using your GitHub account
Received on Monday, 14 October 2019 09:28:28 UTC