[wpt-sync] Sync PR 51302 - Revert "Add WPT for resolving registration and refresh endpoints"
Categories
(Testing :: web-platform-tests, task, P4)
Tracking
(firefox138 fixed)
Tracking | Status | |
---|---|---|
firefox138 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 51302 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/51302
Details from upstream follow.
thefrog <thefrog@chromium.org> wrote:
Revert "Add WPT for resolving registration and refresh endpoints"
This reverts commit 78d84fcea84d92a13777b5f2814d6e8baf5b094e.
Reason for revert: https://crrev.com/c/6348219 landed before this and
requires changes to this CL. But this CL landed without re-running the
build.As a result, this is failing across many builders.
Original change's description:
Add WPT for resolving registration and refresh endpoints
New test: resolving-urls.https.html
Bug: 353767385
Change-Id: Ic35e05da48f87664c9c15adb6e937856c16d11e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6345171
Reviewed-by: Daniel Rubery \<drubery@chromium.org>
Commit-Queue: thefrog \<thefrog@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431606}Bug: 353767385
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Change-Id: I1a42dea619df0d65ca1847b14e287d68f065a287
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349657
Auto-Submit: thefrog \<thefrog@chromium.org>
Commit-Queue: Rubber Stamper \<rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper \<rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1431687}
Assignee | ||
Updated•5 months ago
|
Assignee | ||
Updated•5 months ago
|
Assignee | ||
Comment 1•5 months ago
|
||
Assignee | ||
Comment 2•5 months ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 14 tests and 1 subtests
Status Summary
Firefox
OK
: 1
PASS
: 1
TIMEOUT
: 26
NOTRUN
: 10
Chrome
OK
: 1
PASS
: 1
TIMEOUT
: 26
NOTRUN
: 10
Safari
OK
: 1
PASS
: 1
TIMEOUT
: 26
NOTRUN
: 10
Links
Details
New Tests That Don't Pass
- /device-bound-session-credentials/clear-site-data.https.html [wpt.fyi]:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)- An session ended with Clear-Site-Data: 'cookies' does not refresh cookies:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
) - An session ended with Clear-Site-Data: 'storage' does not refresh cookies:
NOTRUN
(Chrome:NOTRUN
, Safari:NOTRUN
)
- An session ended with Clear-Site-Data: 'cookies' does not refresh cookies:
- /device-bound-session-credentials/create-session.https.html [wpt.fyi]:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)- An established session can refresh a cookie:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)
- An established session can refresh a cookie:
- /device-bound-session-credentials/credentials-matching.https.html [wpt.fyi]:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)- Expires attribute in credentials doesn't affect matching:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
) - Max-Age attribute in credentials doesn't affect matching:
NOTRUN
(Chrome:NOTRUN
, Safari:NOTRUN
) - HttpOnly attribute in credentials affects matching:
NOTRUN
(Chrome:NOTRUN
, Safari:NOTRUN
) - SameSite attribute in credentials affects matching:
NOTRUN
(Chrome:NOTRUN
, Safari:NOTRUN
) - Secure attribute in credentials affects matching:
NOTRUN
(Chrome:NOTRUN
, Safari:NOTRUN
) - Path attribute in credentials affects matching:
NOTRUN
(Chrome:NOTRUN
, Safari:NOTRUN
) - Partition attribute in credentials affects matching:
NOTRUN
(Chrome:NOTRUN
, Safari:NOTRUN
)
- Expires attribute in credentials doesn't affect matching:
- /device-bound-session-credentials/include-site.https.html [wpt.fyi]:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)- An established session refreshes across sites:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)
- An established session refreshes across sites:
- /device-bound-session-credentials/refresh-does-not-send-challenge.https.html [wpt.fyi]:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)- Refresh does not send back Sec-Session-Challenge:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)
- Refresh does not send back Sec-Session-Challenge:
- /device-bound-session-credentials/refresh-replaces-config.https.html [wpt.fyi]:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)- Refresh can replace session config:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)
- Refresh can replace session config:
- /device-bound-session-credentials/refresh-with-continue-false.https.html [wpt.fyi]:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)- A session ended with continue:false does not refresh cookies:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)
- A session ended with continue:false does not refresh cookies:
- /device-bound-session-credentials/registration-sends-challenge.https.html [wpt.fyi]:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)- Registration can send back Sec-Session-Challenge:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)
- Registration can send back Sec-Session-Challenge:
- /device-bound-session-credentials/session-cookie-has-no-attributes.https.html [wpt.fyi]:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)- An established session can refresh a cookie that has all default attributes:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)
- An established session can refresh a cookie that has all default attributes:
- /device-bound-session-credentials/set-authorization.https.html [wpt.fyi]:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)- Session registration sends the authorization value:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)
- Session registration sends the authorization value:
- /device-bound-session-credentials/set-early-challenge.https.html [wpt.fyi]:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)- A challenge can be set ahead of time:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
) - A challenge can be set for multiple sessions ahead of time (single header):
NOTRUN
(Chrome:NOTRUN
, Safari:NOTRUN
) - A challenge can be set for multiple sessions ahead of time (multiple headers):
NOTRUN
(Chrome:NOTRUN
, Safari:NOTRUN
)
- A challenge can be set ahead of time:
- /device-bound-session-credentials/set-scope-origin.https.html [wpt.fyi]:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)- A request within the scope origin refreshes:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
) - A request outside the scope origin does not refresh:
NOTRUN
(Chrome:NOTRUN
, Safari:NOTRUN
)
- A request within the scope origin refreshes:
- /device-bound-session-credentials/set-scope-specification.https.html [wpt.fyi]:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)- Scope specification configuration is respected:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)
- Scope specification configuration is respected:
https://hg.mozilla.org/mozilla-central/rev/4517147640d5
https://hg.mozilla.org/mozilla-central/rev/56bf350bb7e6
Description
•