-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convert to purely screen wake lock #255
Conversation
Breaking changers remain:
@reillyeon, I guess I could revert those too? The WakeLockPermissionDescriptor felt like a bit of overkill, but I guess it does provide some extensibility. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Much thanks!
LGTM overall, punting the review of the remaining breaking changes https://github.com/w3c/wake-lock/pull/255#issuecomment-599514748 to @reillyeon.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good except for a couple places where we should still be using WakeLockType
.
Thanks @reillyeon for chatting all those. Need a day before I jump back into this. |
Ok, sorry for taking a little longer than expected. Hope you are all healthy and well. How should we handle the testing? |
I'd suggest to separate tests into corresponding directories, as WPT's test directories are typically named after the shortname of the spec. And we may reuse some common JS from screen wake lock for system wake lock. |
Thanks @Honry! I guess we need to then split up: @Honry will you be our testing lead for this? It would be great to start matching tests to spec text. @anssiko, @reillyeon, should we request a new shortname for the spec? |
@Honry, lol, sorry, I see you are already listed as our QA lead! 🙌🎉🎊 Can't ask for a better QA lead on this! ReSpec supports |
@marcoscaceres, sure! :) |
Actually the original test links were added by myself. I will update them once tests relocated. |
Ok cool! Let's merge this, and do the test linking independently. |
I've filed a Chromium issue to track the breaking changes. |
Can do this when we publish to /TR. |
This CL renames "wake-lock" to "screen-wake-lock" in policy-controlled feature specific for screen wake lock, and leaves system wake lock's policy control as allowed by default because its associated feature policy is not defined yet. Spec changes at: https://github.com/w3c/wake-lock/pull/255 Bug: 1064685 Change-Id: I7701a532a7688d708a75aedafc8713d671da6e2b
This CL renames "wake-lock" to "screen-wake-lock" in policy-controlled feature specific for screen wake lock, and leaves system wake lock's policy control as allowed by default because its associated feature policy is not defined yet. Spec changes at: https://github.com/w3c/wake-lock/pull/255 Bug: 1064685 Change-Id: I7701a532a7688d708a75aedafc8713d671da6e2b
Make some small corrections after the big changes from that pull request.
…on names. This adapts the implementation to some of the breaking spec changes introduced in w3c/screen-wake-lock#255. Namely, WakeLockPermissionDescriptor has been removed in favor of using a regular PermissionDescriptor object with |name| set to "screen-wake-lock". That spec change also removed system wake locks (and consequently the additions to the WorkerNavigator interface) altogether, but that will be done in a separate CL, so for now we also support a PermissionDescriptor object with |name| set to "system-wake-lock". Bug: 257511, 1064685 Change-Id: I096f3fae24444da5ca6b1eeb3889a813a9e5f270
…on names. This adapts the implementation to some of the breaking spec changes introduced in w3c/screen-wake-lock#255. Namely, WakeLockPermissionDescriptor has been removed in favor of using a regular PermissionDescriptor object with |name| set to "screen-wake-lock". That spec change also removed system wake locks (and consequently the additions to the WorkerNavigator interface) altogether, but that will be done in a separate CL, so for now we also support a PermissionDescriptor object with |name| set to "system-wake-lock". Bug: 257511, 1064685 Change-Id: I096f3fae24444da5ca6b1eeb3889a813a9e5f270
…on names. This adapts the implementation to some of the breaking spec changes introduced in w3c/screen-wake-lock#255. Namely, WakeLockPermissionDescriptor has been removed in favor of using a regular PermissionDescriptor object with |name| set to "screen-wake-lock". That spec change also removed system wake locks (and consequently the additions to the WorkerNavigator interface) altogether, but that will be done in a separate CL, so for now we also support a PermissionDescriptor object with |name| set to "system-wake-lock". Bug: 257511, 1064685 Change-Id: I096f3fae24444da5ca6b1eeb3889a813a9e5f270 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2134228 Reviewed-by: Kentaro Hara <[email protected]> Reviewed-by: Kent Tamura <[email protected]> Reviewed-by: Mounir Lamouri <[email protected]> Reviewed-by: Kinuko Yasuda <[email protected]> Reviewed-by: Reilly Grant <[email protected]> Auto-Submit: Raphael Kubo da Costa <[email protected]> Commit-Queue: Raphael Kubo da Costa <[email protected]> Cr-Commit-Position: refs/heads/master@{#756753}
…on names. This adapts the implementation to some of the breaking spec changes introduced in w3c/screen-wake-lock#255. Namely, WakeLockPermissionDescriptor has been removed in favor of using a regular PermissionDescriptor object with |name| set to "screen-wake-lock". That spec change also removed system wake locks (and consequently the additions to the WorkerNavigator interface) altogether, but that will be done in a separate CL, so for now we also support a PermissionDescriptor object with |name| set to "system-wake-lock". Bug: 257511, 1064685 Change-Id: I096f3fae24444da5ca6b1eeb3889a813a9e5f270 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2134228 Reviewed-by: Kentaro Hara <[email protected]> Reviewed-by: Kent Tamura <[email protected]> Reviewed-by: Mounir Lamouri <[email protected]> Reviewed-by: Kinuko Yasuda <[email protected]> Reviewed-by: Reilly Grant <[email protected]> Auto-Submit: Raphael Kubo da Costa <[email protected]> Commit-Queue: Raphael Kubo da Costa <[email protected]> Cr-Commit-Position: refs/heads/master@{#756753}
…on names. This adapts the implementation to some of the breaking spec changes introduced in w3c/screen-wake-lock#255. Namely, WakeLockPermissionDescriptor has been removed in favor of using a regular PermissionDescriptor object with |name| set to "screen-wake-lock". That spec change also removed system wake locks (and consequently the additions to the WorkerNavigator interface) altogether, but that will be done in a separate CL, so for now we also support a PermissionDescriptor object with |name| set to "system-wake-lock". Bug: 257511, 1064685 Change-Id: I096f3fae24444da5ca6b1eeb3889a813a9e5f270 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2134228 Reviewed-by: Kentaro Hara <[email protected]> Reviewed-by: Kent Tamura <[email protected]> Reviewed-by: Mounir Lamouri <[email protected]> Reviewed-by: Kinuko Yasuda <[email protected]> Reviewed-by: Reilly Grant <[email protected]> Auto-Submit: Raphael Kubo da Costa <[email protected]> Commit-Queue: Raphael Kubo da Costa <[email protected]> Cr-Commit-Position: refs/heads/master@{#756753}
…riptor, use separate permission names., a=testonly Automatic update from web-platform-tests wake lock: Remove WakeLockPermissionDescriptor, use separate permission names. This adapts the implementation to some of the breaking spec changes introduced in w3c/screen-wake-lock#255. Namely, WakeLockPermissionDescriptor has been removed in favor of using a regular PermissionDescriptor object with |name| set to "screen-wake-lock". That spec change also removed system wake locks (and consequently the additions to the WorkerNavigator interface) altogether, but that will be done in a separate CL, so for now we also support a PermissionDescriptor object with |name| set to "system-wake-lock". Bug: 257511, 1064685 Change-Id: I096f3fae24444da5ca6b1eeb3889a813a9e5f270 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2134228 Reviewed-by: Kentaro Hara <[email protected]> Reviewed-by: Kent Tamura <[email protected]> Reviewed-by: Mounir Lamouri <[email protected]> Reviewed-by: Kinuko Yasuda <[email protected]> Reviewed-by: Reilly Grant <[email protected]> Auto-Submit: Raphael Kubo da Costa <[email protected]> Commit-Queue: Raphael Kubo da Costa <[email protected]> Cr-Commit-Position: refs/heads/master@{#756753} -- wpt-commits: 7ab34f7e16b668b470397262b66db4ba915beedd wpt-pr: 22658
…riptor, use separate permission names., a=testonly Automatic update from web-platform-tests wake lock: Remove WakeLockPermissionDescriptor, use separate permission names. This adapts the implementation to some of the breaking spec changes introduced in w3c/screen-wake-lock#255. Namely, WakeLockPermissionDescriptor has been removed in favor of using a regular PermissionDescriptor object with |name| set to "screen-wake-lock". That spec change also removed system wake locks (and consequently the additions to the WorkerNavigator interface) altogether, but that will be done in a separate CL, so for now we also support a PermissionDescriptor object with |name| set to "system-wake-lock". Bug: 257511, 1064685 Change-Id: I096f3fae24444da5ca6b1eeb3889a813a9e5f270 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2134228 Reviewed-by: Kentaro Hara <[email protected]> Reviewed-by: Kent Tamura <[email protected]> Reviewed-by: Mounir Lamouri <[email protected]> Reviewed-by: Kinuko Yasuda <[email protected]> Reviewed-by: Reilly Grant <[email protected]> Auto-Submit: Raphael Kubo da Costa <[email protected]> Commit-Queue: Raphael Kubo da Costa <[email protected]> Cr-Commit-Position: refs/heads/master@{#756753} -- wpt-commits: 7ab34f7e16b668b470397262b66db4ba915beedd wpt-pr: 22658
Closes #254
Closes #253
Closes #232
BREAKING CHANGES:
WakeLockPermissionDescriptor
, just use "screen-wake-lock".The following tasks have been completed:
Implementation commitment:
Preview | Diff