[wpt-sync] Sync PR 43670 - Remove scroll-to-text-fragment from SlowTests
Categories
(Testing :: web-platform-tests, task, P4)
Tracking
(firefox122 fixed)
| Tracking | Status | |
|---|---|---|
| firefox122 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 43670 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/43670
Details from upstream follow.
David Bokan <bokan@chromium.org> wrote:
Remove scroll-to-text-fragment from SlowTests
WPT tests should be using the "timeout" meta rather than beign added to
SlowTests, see:
https://bugs.chromium.org/p/chromium/issues/detail?id=758892#c5Bug: 1293315,1133836
Change-Id: I0d8803d56617d4cccc0f77bcb6c4e50d88988e7e
Reviewed-on: https://chromium-review.googlesource.com/5122372
WPT-Export-Revision: 6cbc57f688bc21b6e59860c87645f17f7fe05586
| Assignee | ||
Comment 1•2 years ago
|
||
| Assignee | ||
Comment 2•2 years ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 2 tests and 14 subtests
Status Summary
Firefox
OK : 2
PASS : 4
FAIL : 18
Chrome
OK : 2
PASS : 22
Safari
OK : 1
PASS : 12
FAIL : 5
TIMEOUT: 2
NOTRUN : 4
Links
Details
Firefox-only Failures
- /scroll-to-text-fragment/redirects.html [wpt.fyi]
- Text fragment works from HTTP 301 redirect.:
FAIL - Text fragment works from HTTP 302 redirect.:
FAIL - Text fragment works from HTTP 303 redirect.:
FAIL - Text fragment works from HTTP 307 redirect.:
FAIL - Text fragment works from HTTP 308 redirect.:
FAIL - Text fragment propagated through HTTP 301 redirect.:
FAIL - Text fragment propagated through HTTP 302 redirect.:
FAIL - Text fragment propagated through HTTP 303 redirect.:
FAIL - Text fragment propagated through HTTP 307 redirect.:
FAIL - Text fragment propagated through HTTP 308 redirect.:
FAIL - Text fragment works on client-side location redirect.:
FAIL - Text fragment works on client-side meta redirect.:
FAIL
- Text fragment works from HTTP 301 redirect.:
New Tests That Don't Pass
- /scroll-to-text-fragment/force-load-at-top.html [wpt.fyi]
- force-load-at-top must block scroll on load from element fragment.:
FAIL(Chrome:PASS, Safari:FAIL) - force-load-at-top must block scroll on load from history scroll restoration.:
FAIL(Chrome:PASS, Safari:TIMEOUT) - no-force-load-at-top must not block scroll on load from text fragment.:
FAIL(Chrome:PASS, Safari:NOTRUN) - no-force-load-at-top must not block scroll on load from text fragment with element fallback.:
FAIL(Chrome:PASS, Safari:NOTRUN)
- force-load-at-top must block scroll on load from element fragment.:
- /scroll-to-text-fragment/redirects.html [wpt.fyi]
- Text fragment works from HTTP 301 redirect.:
FAIL(Chrome:PASS, Safari:PASS) - Text fragment works from HTTP 302 redirect.:
FAIL(Chrome:PASS, Safari:PASS) - Text fragment works from HTTP 303 redirect.:
FAIL(Chrome:PASS, Safari:PASS) - Text fragment works from HTTP 307 redirect.:
FAIL(Chrome:PASS, Safari:PASS) - Text fragment works from HTTP 308 redirect.:
FAIL(Chrome:PASS, Safari:PASS) - Text fragment propagated through HTTP 301 redirect.:
FAIL(Chrome:PASS, Safari:PASS) - Text fragment propagated through HTTP 302 redirect.:
FAIL(Chrome:PASS, Safari:PASS) - Text fragment propagated through HTTP 303 redirect.:
FAIL(Chrome:PASS, Safari:PASS) - Text fragment propagated through HTTP 307 redirect.:
FAIL(Chrome:PASS, Safari:PASS) - Text fragment propagated through HTTP 308 redirect.:
FAIL(Chrome:PASS, Safari:PASS) - Text fragment works on client-side location redirect.:
FAIL(Chrome:PASS, Safari:PASS) - Text fragment works on client-side meta redirect.:
FAIL(Chrome:PASS, Safari:PASS) - One text fragment per user gesture allowed in client-side location redirect.:
FAIL(Chrome:PASS, Safari:FAIL) - One text fragment per user gesture allowed in client-side meta redirect.:
FAIL(Chrome:PASS, Safari:FAIL)
- Text fragment works from HTTP 301 redirect.:
Comment 4•2 years ago
|
||
| bugherder | ||
Description
•