- From: Andrey Logvinov via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Jul 2017 15:37:49 +0000
- To: public-device-apis-log@w3.org
@dontcallmedom @anssiko having studied the Feature Policy spec, I wonder if supporting a sandbox flag is needed at all if we are going to support feature policy for wake lock. It looks like the only use of sandbox not covered by the Feature Policy spec would be to explicitly deny wake locks to a same-origin nested browser context, if we have "self" as the default policy for wake locks (not in the spec yet). Also in order to support feature policy we need to make "self" as the default policy rather than explicit same-origin requirement which overrides any policy. Another problem with sandbox flags is that they are all explicitly listed in the HTML spec which necessitates changes to the HTML spec itself, but with feature policy we can specify the feature name in the Wake Lock spec itself, as the Feature Policy spec places no restrictions on feature name set and simply allows the user agent to ignore feature names it does not recognize. -- GitHub Notification of comment by andrey-logvinov Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/51#issuecomment-315791764 using your GitHub account
Received on Monday, 17 July 2017 15:37:54 UTC