> In particular, I wonder if we should remove: > > > The [PERMISSIONS] API provides a uniform way for websites to request permissions from users and query which permissions they have. > > That's just a "statement of fact". This plan sounds OK to me at least. > My suggestion is that we keep the "screen-wake-lock" permission (which is used with Permission Policy - i.e., the HTTP header and `allow=`), but we then drop "screen-wake-lock" from the Permission spec itself. > > We can always add it back later? Hmm, given the discussions in w3c/permissions#247 and that Chromium does implement this integration with the Permissions API, is there a specific reason for changing course here? -- GitHub Notification of comment by rakuco Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/issues/324#issuecomment-906206546 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Thursday, 26 August 2021 08:32:40 UTC
This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:59 UTC