commit 6c6e5c6f3634b13cd3af019ca31edbf73fb7cf93
author W. James MacLean <wjmaclean@chromium.org> Mon Nov 06 22:27:27 2023
committer Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Mon Nov 06 22:59:23 2023
tree 186c15c6b1dafd53051dc5ffd9b891f0011001f6
parent de16754df2ebdef037075d03ef2a9413d8fc6403

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 <dom@chromium.org>
Commit-Queue: W. James Maclean <wjmaclean@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1220552}