Skip to content
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

[wakelock] Rename feature policy #22472

Merged
merged 1 commit into from Mar 30, 2020
Merged

Conversation

@chromium-wpt-export-bot
Copy link
Collaborator

chromium-wpt-export-bot commented Mar 26, 2020

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
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2119886
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Wanming Lin <wanming.lin@intel.com>
Cr-Commit-Position: refs/heads/master@{#754385}

Copy link
Collaborator

wpt-pr-bot left a comment

The review process for this patch is being conducted in the Chromium project.

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-2119886 branch from 00e0df3 to c558953 Mar 27, 2020
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
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2119886
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Wanming Lin <wanming.lin@intel.com>
Cr-Commit-Position: refs/heads/master@{#754385}
@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-2119886 branch from c558953 to e441612 Mar 30, 2020
@chromium-wpt-export-bot chromium-wpt-export-bot merged commit c84b772 into master Mar 30, 2020
13 checks passed
13 checks passed
Azure Pipelines Build #20200330.7 succeeded
Details
Azure Pipelines (./wpt test-jobs) ./wpt test-jobs succeeded
Details
Azure Pipelines (affected tests without changes: Safari Technology Preview) affected tests without changes: Safari Technology Preview succeeded
Details
Azure Pipelines (affected tests: Safari Technology Preview) affected tests: Safari Technology Preview succeeded
Details
Azure Pipelines (wpt.fyi hook: safari-preview-affected-tests) wpt.fyi hook: safari-preview-affected-tests succeeded
Details
Azure Pipelines (wpt.fyi hook: safari-preview-affected-tests-without-changes) wpt.fyi hook: safari-preview-affected-tests-without-changes succeeded
Details
Community-TC (pull_request) TaskGroup: success
Details
staging.wpt.fyi - chrome[experimental] Chrome results
Details
staging.wpt.fyi - firefox[experimental] Firefox results
Details
staging.wpt.fyi - safari[experimental] Safari results
Details
wpt.fyi - chrome[experimental] Chrome results
Details
wpt.fyi - firefox[experimental] Firefox results
Details
wpt.fyi - safari[experimental] Safari results
Details
@chromium-wpt-export-bot chromium-wpt-export-bot deleted the chromium-export-cl-2119886 branch Mar 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.