Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bug 1863416 [wpt PR 42982] - Some WPT tests should run same-process o…
…nly., a=testonly Automatic update from web-platform-tests Some WPT tests should run same-process only. In preparation for enabling isolated sandboxed iframes by default, there are some WPT tests that should not be allowed to run with origin process isolation. In each case the affected tests are forced to remain same- process by placing them in the not-site-per-process virtual test suite. drag-drop-same-unique-origin.html uses EventSender, and although its src and target frames are same process, under isolated sandboxed iframes that process would be remote to the mainframe, which EventSender will not support. The longtask* tests all use window.PerformanceLongTaskTiming, which inherently does not support cross-process frames. The tests want to exercise data coming from a cross-origin, same-site child frame, and the safest way to ensure that is to force the frames to remain same- process. Note: the cross-origin longtask tests were using sandboxed-srcdoc frames to simulate being cross-origin (and same-process, since WPT tests default to process-per-origin), but there's no need for that if the test is run in not-site-per-process. Therefore the tests have been revised to be non-sandboxed cross-origin using WPT apis, resulting in tests that are hopefully easier to understand. Bug: 550122 Change-Id: Id104439fd34ba0ebb94a516224a21fd832c65828 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5006758 Reviewed-by: Dominic Farolino <[email protected]> Commit-Queue: W. James Maclean <[email protected]> Cr-Commit-Position: refs/heads/main@{#1220552} -- wpt-commits: 6c6e5c6f3634b13cd3af019ca31edbf73fb7cf93 wpt-pr: 42982
- Loading branch information