- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Oct 2022 04:54:25 +0000
- To: public-device-apis-log@w3.org
> How about we keep using NotAllowedError (so I don't need to try to consider whether this change will break compatibility with what we've shipped in Chromium) and specify the messages for each of the failure types That still feels kinda not right to me. My preference would be to use the exception types, as there is plenty of precedence (https://github.com/w3c/screen-wake-lock/issues/352#issuecomment-1261611533) at least for `InvalidStateError` for non-fully active. -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/issues/352#issuecomment-1271108195 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 7 October 2022 04:54:27 UTC