Run same tests for layout-2020 and layout-2013 (#30092)

Most tests were only being run for layout-2013, not for layout-2020.
This wasn't great since layout-2020 is now the default.

So this patch unifies the lists of included tests for both layouts.
For layout-2013 this implies adding css/css-content/, css/css-logical/
and css/css-masking/clip/.
For layout-2020 this implies adding several additional css tests, and
also tests like dom/, js/, html/, etc.
This commit is contained in:
Oriol Brufau 2023-08-15 02:28:32 +02:00 committed by GitHub
parent 78c7011240
commit 963104e5fc
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4797 changed files with 679983 additions and 5390 deletions

View file

@ -0,0 +1,4 @@
[browsing_context_name.html]
expected: TIMEOUT
[Retaining window.name on history traversal]
expected: TIMEOUT

View file

@ -0,0 +1,4 @@
[browsing_context_name_cross_origin.html]
expected: TIMEOUT
[Restoring window.name on cross-origin history traversal]
expected: TIMEOUT

View file

@ -0,0 +1,3 @@
[browsing_context_name_cross_origin_2.html]
[Restoring window.name on cross-origin history traversal]
expected: FAIL

View file

@ -0,0 +1,3 @@
[browsing_context_name_cross_origin_3.html]
[Restoring window.name on cross-origin history traversal]
expected: FAIL

View file

@ -0,0 +1,6 @@
[document-state.https.html]
[A navigation's initiator origin and referrer are stored in the document state and used in the document repopulation case]
expected: FAIL
[A navigation's initiator origin and referrer are stored in the document state and used on location.reload()]
expected: FAIL

View file

@ -1,3 +0,0 @@
[history-traversal-navigate-parent-while-child-loading.html]
[pushState() in parent while child is doing initial navigation, then go back]
expected: FAIL

View file

@ -1,3 +1,4 @@
[history-traversal-navigates-multiple-frames.html]
expected: TIMEOUT
[A history traversal should be able to navigate a parent and child simultaneously]
expected: FAIL
expected: TIMEOUT

View file

@ -0,0 +1,7 @@
[resume-timer-on-history-back.html]
expected: TIMEOUT
[history.back() handles top level page timer correctly]
expected: TIMEOUT
[history.back() handles nested iframe timer correctly]
expected: NOTRUN

View file

@ -0,0 +1,6 @@
[scroll-restoration-basic.html]
[Default value is "auto"]
expected: FAIL
[Invalid values are ignored]
expected: FAIL

View file

@ -1,4 +1,4 @@
[scroll-restoration-fragment-scrolling-cross-origin.html]
expected: ERROR
expected: TIMEOUT
[Manual scroll restoration should take precedent over scrolling to fragment in cross origin navigation]
expected: TIMEOUT

View file

@ -0,0 +1,3 @@
[scroll-restoration-navigation-cross-origin.html]
[Navigating to new page should reset to "auto" and navigating back should restore and respect scroll restoration mode]
expected: FAIL

View file

@ -0,0 +1,3 @@
[scroll-restoration-navigation-samedoc.html]
[history.{push,replace}State retain scroll restoration mode and navigation in the same document respects it]
expected: FAIL

View file

@ -0,0 +1,3 @@
[popstate_event.html]
[Queue a task to fire popstate event]
expected: FAIL

View file

@ -0,0 +1,4 @@
[same-url.html]
expected: TIMEOUT
[Test same-URL navigation and its effects on history]
expected: TIMEOUT

View file

@ -0,0 +1,3 @@
[scroll-restoration-order.html]
[Traversing history should restore scroll position after dispatching popstate and before dispatching hashchange]
expected: FAIL

View file

@ -0,0 +1,3 @@
[window-name-after-cross-origin-main-frame-navigation.sub.html]
[window.name should equal "" after a cross-origin main frame navigation]
expected: FAIL