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

PlzDedicatedWorker: send COEP violation reports to an environment settings object owner #28364

Merged
merged 1 commit into from Apr 9, 2021

Conversation

@chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Apr 5, 2021

This CL makes a dedicated worker sends COEP violation reports to its
an environment settings object owner during the worker initialization
process when cross-origin-embedder-policy is invalid.
For PlzDedicatedWorker, the owner is the creator document or worker
which starts the worker directly.
For non-PlzDedicatedWorker, the owner is the nearest ancestor frame to
keep the current behavior.

Bug: 1060837, 1197041
Change-Id: I088470e7355c94f48b6ac8d51b5cf813b9d181ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2794353
Commit-Queue: Asami Doi <asamidoi@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#870917}

Copy link
Collaborator

@wpt-pr-bot 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 changed the title PlzDedicatedWorker: send COEP violation reports to its owner frame PlzDedicatedWorker: send COEP violation reports to an environment settings object owner Apr 5, 2021
@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-2794353 branch 3 times, most recently from 5af9c8d to 9c3b533 Apr 5, 2021
…tings object owner

This CL makes a dedicated worker sends COEP violation reports to its
an environment settings object owner during the worker initialization
process when cross-origin-embedder-policy is invalid.
For PlzDedicatedWorker, the owner is the creator document or worker
which starts the worker directly.
For non-PlzDedicatedWorker, the owner is the nearest ancestor frame to
keep the current behavior.

Bug: 1060837, 1197041
Change-Id: I088470e7355c94f48b6ac8d51b5cf813b9d181ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2794353
Commit-Queue: Asami Doi <asamidoi@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#870917}
@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-2794353 branch from 9c3b533 to 1282222 Apr 9, 2021
@chromium-wpt-export-bot chromium-wpt-export-bot merged commit 6385045 into master Apr 9, 2021
23 checks passed
23 checks passed
@azure-pipelines
Azure Pipelines Build #20210409.14 succeeded
Details
@azure-pipelines
Azure Pipelines (./wpt test-jobs) ./wpt test-jobs succeeded
Details
@azure-pipelines
Azure Pipelines (affected tests without changes: Safari Technology Preview) affected tests without changes: Safari Technology Preview succeeded
Details
@azure-pipelines
Azure Pipelines (affected tests: Safari Technology Preview) affected tests: Safari Technology Preview succeeded
Details
@azure-pipelines
Azure Pipelines (wpt.fyi hook: safari-preview-affected-tests) wpt.fyi hook: safari-preview-affected-tests succeeded
Details
@azure-pipelines
Azure Pipelines (wpt.fyi hook: safari-preview-affected-tests-without-changes) wpt.fyi hook: safari-preview-affected-tests-without-changes succeeded
Details
@community-tc-integration
download-firefox-nightly Community-TC (pull_request)
Details
@community-tc-integration
lint Community-TC (pull_request)
Details
@community-tc-integration
sink-task Community-TC (pull_request)
Details
@staging-wpt-fyi
staging.wpt.fyi - chrome[experimental] Chrome results
Details
@staging-wpt-fyi
staging.wpt.fyi - firefox[experimental] Firefox results
Details
@staging-wpt-fyi
staging.wpt.fyi - safari[experimental] Safari results
Details
@community-tc-integration
update-built Community-TC (pull_request)
Details
@community-tc-integration
wpt-chrome-dev-results Community-TC (pull_request)
Details
@community-tc-integration
wpt-chrome-dev-results-without-changes Community-TC (pull_request)
Details
@community-tc-integration
wpt-chrome-dev-stability Community-TC (pull_request)
Details
@community-tc-integration
wpt-decision-task Community-TC (pull_request)
Details
@community-tc-integration
wpt-firefox-nightly-results Community-TC (pull_request)
Details
@community-tc-integration
wpt-firefox-nightly-results-without-changes Community-TC (pull_request)
Details
@community-tc-integration
wpt-firefox-nightly-stability Community-TC (pull_request)
Details
@wpt-fyi
wpt.fyi - chrome[experimental] Chrome results
Details
@wpt-fyi
wpt.fyi - firefox[experimental] Firefox results
Details
@wpt-fyi
wpt.fyi - safari[experimental] Safari results
Details
@chromium-wpt-export-bot chromium-wpt-export-bot deleted the chromium-export-cl-2794353 branch Apr 9, 2021
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