Automatic update from web-platform-tests
Verify that COOP severed the relationship on the Opener's side, with the popup's initial Browsing context closed. (#21161)
* Add an assertion on the Opener's WindowProxy, verifying that COOP severed the relationship bothways
* Remove defunct comment
* Trigger the popup closure during the test cleanup using the broadcast channel
* Close the popup from the top level opened document in COOP tests, also test opener's window proxy on some more tests
* Fix typos and style
* Fix failing cleanup in blob-popup.https.html
--
wpt-commits: 3624a87d4176e814d2e67cfa5e427bc217c9c5b0
wpt-pr: 21161
Automatic update from web-platform-tests
Rewrite referrer-origin-when-cross-origin.js using get_host_info (#21292)
This will allow WebKit to pass these tests when running the tests
in the WebKit test harness.
--
wpt-commits: 16bc186789dee7144745486ef7a744940e3f2dae
wpt-pr: 21292
Automatic update from web-platform-tests
Portals: Mark portals-focus.sub.html as long
Bug: 1043455
Change-Id: Ifa7202ec2379446e2c19c593bf45d8a2528f6160
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011165
Commit-Queue: Lucas Gadani <lfg@chromium.org>
Reviewed-by: Lucas Gadani <lfg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#733578}
--
wpt-commits: 829c76923332d0f2e761bdd34925aaa87065b59f
wpt-pr: 21276
Automatic update from web-platform-tests
COOP+COEP: more flaky test measures
Helps with #21107.
--
wpt-commits: 8029b15fd4ae46dd7a4696b9bbf63b1b4229fb47
wpt-pr: 21274
Automatic update from web-platform-tests
Referrer Policy: inheritance with javascript: URLs and document.write()
This cleans up some existing tests and adds new tests with results I expect from reading the specification, but do not see confirmed in implementations.
--
wpt-commits: da44ef2f35865d73b7e32393142754f3e0ac859a
wpt-pr: 21232
Automatic update from web-platform-tests
Attempt to fix flaky timeout in resource_timing_buffer_full_eventually
This CL attempts to fix the flaky timeouts in the test
virtual/omt-worker-fetch/external/wpt/resource-timing/resource_timing_buffer_full_eventually.html
by doing the following:
1. Set it to be 'long'. This is a slow test due to the large amount of
fetches.
2. Set the number of elements added at a time to 8, which is faster than
100 in my experimentation.
3. Do not wait for onload to begin appending scripts.
Bug: 1041707
Change-Id: Iddf37a72135e1f82c23c3e71c8da40eca13b8f78
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011294
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#733502}
--
wpt-commits: 81038142ac0e8e89eee3fb7700d128c830e9985b
wpt-pr: 21279
Automatic update from web-platform-tests
ServiceWorker: Remove controlled frames using add_cleanup() helper
clients-matchall-client-types.https.html manually cleans up controlled frames at
the end of each test case. This doesn't work when the tests fail on the
way, and that unexpectedly prolongs lifetime of a service worker. This is the
reason why the second test failed with the following message.
"Error: wait_for_state must be passed a ServiceWorker"
This CL fixes it by cleaning up the frames using add_cleanup() helper.
Bug: n/a
Change-Id: I0f0e71a55814d114665eff824c917c918ac993f1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010600
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#733498}
--
wpt-commits: 5b9513ad4a697667b7f0a9c93e4a89b83c1bfc0c
wpt-pr: 21282
Automatic update from web-platform-tests
[LargestContentfulPaint] Add multiple redirect test
This CL adds the equivalent to element-timing/multiple-redirects for
LargestContentfulPaint. Since we use get-host-info instead of the .sub
commands, the .sub in the name is unneeded. This CL also updates the
expectations for disabled-OOR-CORS: the recent TAO tests will fail
without this flag enabled.
Bug: 1003943, 1042580
Change-Id: Ibc0b79d4c548fdbe9dc3eab6bd810f5a92425b35
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010176
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#733408}
--
wpt-commits: 46a8fb0048edf5f8304e69cc463bea23be830e2b
wpt-pr: 21271
--HG--
rename : testing/web-platform/tests/element-timing/multiple-redirects-TAO.sub.html => testing/web-platform/tests/element-timing/multiple-redirects-TAO.html
These prefs got disabled for Late Beta and Release in bug 1611454 but the test
uses the feature (access to media devices from frame).
Differential Revision: https://phabricator.services.mozilla.com/D61093
--HG--
extra : moz-landing-system : lando
Related to bug 1608121.
When we use Ion and WebAssembly, we might get multiple return values
from function calls. This patch refactors the direct JS-to-Wasm-via-Ion
call path to better support multiple values.
The patch adds a safepoint at the call, as appears to be necessary in
general, and also when results are captured as MIR values. There is a
slight optimization in that void-returning Wasm functions just get a
MConstant result that's visible to the optimizer.
Differential Revision: https://phabricator.services.mozilla.com/D60228
--HG--
extra : moz-landing-system : lando
The following methods are removed:
1. notifyChannelClassifierProtectionDisabled
2. notifyCookieAllowed
3. notifyCookieBlocked
Depends on D56875
Differential Revision: https://phabricator.services.mozilla.com/D57630
--HG--
extra : moz-landing-system : lando
This patch does the followings:
1. Remove NotifyOnContentBlocking in WindowOuter and all the call sites.
This is because all the content blocking event handling is moved to the parent.
2. Replace UrlClassifierCommon::NotifyChannelBlocked with AntiTrackingCommon:::NotifyContentBlockingEventInParent.
This is because we don't need to pass the request to the child anymore, which was implemented in NotifyChannelBlocked previously.
3. Add NotifyContentBlockingEvent* utility functions to AntiTrackingCommon.cpp.
4. Update AntiTrackingCommon::NotifyBlockingDecision, when it is called in the parent,
do not send requests to the child, notify the parent directly
Depends on D56874
Differential Revision: https://phabricator.services.mozilla.com/D56875
--HG--
extra : moz-landing-system : lando
At this point, there is no consumer that uses ContentBlockingLog stored
in the child. This patch removes the following code:
1. Removing nsGlobalWindowOuter::NotifyContentBlockingEvent
2. Removing nsDocLoader::OnContentBlockingEvent
3. Removing contentBlockingEvent in nsISecureBrowserUI.idl
4. Removing mContentBlockingLog from Document.cpp and APIs related to it.
Differential Revision: https://phabricator.services.mozilla.com/D56874
--HG--
extra : moz-landing-system : lando
