[wpt-sync] Sync PR 51391 - Add WPT for multiple credentials in session instructions
Categories
(Core :: CSS Parsing and Computation, task, P4)
Tracking
()
Tracking | Status | |
---|---|---|
firefox138 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 51391 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/51391
Details from upstream follow.
thefrog <thefrog@chromium.org> wrote:
Add WPT for multiple credentials in session instructions
New test: multiple-credentials.https.html
Bug: 353767385
Change-Id: I5a43c981efb7c1fd5bb54181a77167006df394dd
Reviewed-on: https://chromium-review.googlesource.com/6354226
WPT-Export-Revision: b21e4c09174eb80304dc68e9c592102b6a1aff8f
Assignee | ||
Comment 1•1 month ago
|
||
Assignee | ||
Updated•1 month ago
|
Assignee | ||
Comment 2•1 month ago
|
||
Assignee | ||
Comment 3•1 month ago
|
||
CI Results
Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 6 tests and 3 subtests
Status Summary
Firefox
TIMEOUT
: 12
NOTRUN
: 9
Chrome
TIMEOUT
: 12
NOTRUN
: 9
Safari
TIMEOUT
: 12
NOTRUN
: 9
Links
Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base
Details
New Tests That Don't Pass
- /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/multiple-credentials.https.html [wpt.fyi]:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)- A session can have multiple credentials set:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)
- A session can have multiple credentials set:
- /device-bound-session-credentials/multiple-registrations.https.html [wpt.fyi]:
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
)- Multiple registrations can be triggered in one response (single header):
TIMEOUT
(Chrome:TIMEOUT
, Safari:TIMEOUT
) - Multiple registrations can be triggered in one response (multiple headers):
NOTRUN
(Chrome:NOTRUN
, Safari:NOTRUN
)
- Multiple registrations can be triggered in one response (single header):
- /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/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-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:
https://hg.mozilla.org/mozilla-central/rev/c7f15b461468
https://hg.mozilla.org/mozilla-central/rev/a6102a629702
Description
•