- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Nov 2020 15:48:34 +0000
- To: public-web-nfc@w3.org
My take: from this [keyboard lock issue discussion](https://github.com/WICG/keyboard-lock/issues/35) it seems the reason to choose `InvalidStateError` was specific to their case. I'd use `NotAllowedError` as suggested [in this comment](https://github.com/WICG/keyboard-lock/issues/35#issuecomment-387230960), or `SecurityError`, since it's a failure because of a security policy, and invalid state error is a bit confusing on what exactly it refers to (and where/how that state is defined). On ContactPicker looks like a copy from the previous choice :). I'd avoid making a de-facto standard choice from an application specific choice. IMHO we need a more generic relevant error type. I agree we should do it in similar way in the Web Platform, but then this requires a discussion/decision in the Web Platform. -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/pull/610#issuecomment-734370892 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 November 2020 15:48:36 UTC