- From: François Beaufort via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Nov 2019 06:26:51 +0000
- To: public-web-nfc@w3.org
I understand where this is coming from, but I'm not sure we should throw a TypeError for scan options as this is technically NOT an invalid filter. It's just that scan won't trigger any onreading event. I'm afraid we'd make it more complicated to cover all cases. For instance, should we throw a TypeError when NDEFScanOptions `recordType` is set to `FOO`? I'll let other chime as I don't feel strongly about it. -- GitHub Notification of comment by beaufortfrancois Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/437#issuecomment-550165169 using your GitHub account
Received on Wednesday, 6 November 2019 06:26:53 UTC