-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[Security][Coop] Browsing context switch reporting WPT #23670
Conversation
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.
The review process for this patch is being conducted in the Chromium project.
c9693f0
to
d9acb68
Compare
54eced9
to
0eb2590
Compare
9b67146
to
acefb9b
Compare
acefb9b
to
207741b
Compare
This CL adds basic reporting tests for browsing context switches. It provides a reporting endpoint (report.py), and reusable helpers within reporting-common.js, allowing future tests. The helpers provided verify that expected report templates are present on the expected endpoints, and that no extraneous reports are present. This CL only convers the cases: Popup opened from pages with coop : Same-origin with report only navigating to * Same-origin (without report) navigatin to *-with report Follow ups will cover redirects (moved to follow up as it had timeout issues), other origins and iframe cases. Bug: 1076456 Change-Id: I7a39d4def20692d8628ce2406569638310684f4f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2207451 Reviewed-by: Arthur Sonzogni <[email protected]> Commit-Queue: Pâris Meuleman <[email protected]> Auto-Submit: Pâris Meuleman <[email protected]> Cr-Commit-Position: refs/heads/master@{#776008}
207741b
to
8cc2a71
Compare
The following test failed on wpt-chrome-dev-stability Slow tests
|
@stephenmcgruer The Taskcluster failure is caused by a timeout. I did see some failing tests in the log but there is no unstable result. Could you admin merge? #7660 |
Huh, I wanted to say that the correct action is to mark the test timeout=long, but it appears to already be so. Ok, admin-merging. |
This CL adds basic reporting tests for browsing context switches.
It provides a reporting endpoint (report.py), and reusable helpers
within reporting-common.js, allowing future tests.
The helpers provided verify that expected report templates are present
on the expected endpoints, and that no extraneous reports are present.
This CL only convers the cases:
Popup opened from pages with coop :
Same-origin with report only navigating to *
Same-origin (without report) navigatin to *-with report
Follow ups will cover redirects (moved to follow up as it had timeout
issues), other origins and iframe cases.
Bug: 1076456
Change-Id: I7a39d4def20692d8628ce2406569638310684f4f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2207451
Reviewed-by: Arthur Sonzogni <[email protected]>
Commit-Queue: Pâris Meuleman <[email protected]>
Auto-Submit: Pâris Meuleman <[email protected]>
Cr-Commit-Position: refs/heads/master@{#776008}