Remove several Navigation API tests

[farre]

Test List

Test List

Ordering and transition

navigation-api/ordering-and-transition/navigate-204-205-download-then-same-document.html
navigation-api/ordering-and-transition/back-same-document-intercept.html?no-currententrychange
navigation-api/ordering-and-transition/back-same-document-intercept.html?currententrychangel

Scroll Behavior

navigation-api/scroll-behavior/manual-scroll-fragment-does-not-exist.html
navigation-api/scroll-behavior/manual-scroll-reload-no-scroll-anchoring.html
navigation-api/scroll-behavior/after-transition-reload-no-scroll-anchoring.html

Rational

The tests are not interoperable with specification.

See PR:s web-platform-tests/wpt-metadata#8337, web-platform-tests/wpt-metadata#8338, and web-platform-tests/wpt-metadata#8339

Rationale

No response

[farre]

@foolip

[nt1m]

Since these tests are already interoperable across Safari and Chrome:

https://wpt.fyi/results/navigation-api?label=master&label=experimental&aligned&q=navigate-204-205-download-then-same-document.html%20or%20back-same-document-intercept.html%3Fno-currententrychange%20or%20back-same-document-intercept.html%3Fcurrententrychange%20or%20manual-scroll-fragment-does-not-exist.html%20or%20manual-scroll-reload-no-scroll-anchoring.html%20or%20after-transition-reload-no-scroll-anchoring.html

I wonder if it makes more sense to change the spec instead? Unless there's a good developer experience reason to keep the spec as it is.

@noamr @annevk @basuke @RupinMittal Any thoughts?

[farre]

The scroll tests could maybe be kept as is with spec changes, but web-platform-tests/wpt-metadata#8337 is the issue with #wait-for-all, and there the developer experience is not good enough if spec isn't followed.

But regardless of if spec or test should change the tests should be excluded from Interop 2025, since they are currently not reflecting spec and need some kind of change to happen.

[annevk]

Excluding from Interop seems very reasonable. Removing the tests less so. I'd support renaming them to include tentative + a specification issue / PR.

[noamr]

I think we should remove them from the interop list and then continue the spec discussion.

[nt1m]

Excluding from Interop seems fine to me, but it would be good to try to resolve the spec discussion

[noamr]

Excluding from Interop seems fine to me, but it would be good to try to resolve the spec discussion

Yes, absolutely. Those spec discussions are ongoing. Would love to hear some opinions from webkit about them.
Specifically whatwg/html#11845

[nt1m]

Do we have an issue for the scroll behavior?

[farre]

We have web-platform-tests/wpt#56855 for the scrolling tests.

[farre]

Merged and closing.