Closed Bug 1568104 Opened 6 years ago Closed 5 years ago

[wpt-sync] Sync PR 17989 - Port WebSocket 3p-cookie-blocking web tests to wpt_internal

Categories

(Core :: Networking: WebSockets, task, P5)

task

Tracking

()

RESOLVED FIXED
mozilla70
Tracking Status
firefox70 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [necko-triaged][wptsync downstream])

Sync web-platform-tests PR 17989 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/17989
Details from upstream follow.

Lily Chen <chlily@chromium.org> wrote:

Port WebSocket 3p-cookie-blocking web tests to wpt_internal

(For context, see https://crrev.com/c/1691522.)

The new requirement that SameSite=None cookies must be Secure made it
impossible to properly test third party cookies on WebSocket because
the web_test runner does not have a wss server. This CL ports those
tests, formerly in web_tests/http/tests/security/cookies/websocket/,
to web_tests/wpt_internal/websocket-cookies/.

Bug: none
Change-Id: Ifc6d2d78a84aa6c93e297dc71b3595108a18f179

Reviewed-on: https://chromium-review.googlesource.com/1713670
WPT-Export-Revision: 8c2fbad4a245a52c7b5384718ab1e5446b325d1e

Component: web-platform-tests → Networking: WebSockets
Product: Testing → Core
Priority: P4 → P5
Whiteboard: [wptsync downstream] → [necko-triaged][wptsync downstream]
Ran 1 tests and 1 subtests OK : 1 FAIL : 1 New tests that have failures or other problems: /websockets/cookies/third-party-cookie-accepted.https.html Test that third-party cookies are accepted for WebSockets.: FAIL
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/605be81220d9 [wpt PR 17989] - Port WebSocket 3p-cookie-blocking web tests to wpt_internal, a=testonly https://hg.mozilla.org/integration/mozilla-inbound/rev/e4abe7c75be5 [wpt PR 17989] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
You need to log in before you can comment on or make changes to this bug.