- From: Martin Thomson via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Aug 2021 04:24:43 +0000
- To: public-device-apis-log@w3.org
I find that argument convincing. If no UA is going to implement this as a permission, then that makes sense. If we can standardize behaviour that has no permissions, that is best for all involved. If we have to add permissions in the future, I don't think that would prevent us from doing so. I am merely willing to accept that Chrome might want to manage this as a permission. One thing to add though: Are we not considering using Permissions Policy to control this? That is, might sites want to prevent nested browsing contexts accessing the feature? That might suggest that there is still some value in the integration. -- GitHub Notification of comment by martinthomson Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/issues/324#issuecomment-906915603 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 27 August 2021 04:24:45 UTC