Closed Bug 1864479 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 43118 - [SAA] Prototyping non-cookie extension (Part 9: shared worker)

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Ari Chivukula <arichiv@chromium.org> wrote:

[SAA] Prototyping non-cookie extension (Part 9: shared worker)

The Storage Access API provides access to unpartitioned cookies in
third-party contexts. This CL is part of a series to extend that access
to non-cookie storage/communication mechanisms.

This CL only includes shared worker as a next step for
the new access. We want to be deliberate adding new mechanisms
since we need good testing and security review here.

All access is restricted to experimental contexts for now, no stable
access or origin trial timeline has been published.

Explainer:
https://arichiv.github.io/saa-non-cookie-storage/

Intent to Prototype:
https://groups.google.com/a/chromium.org/g/blink-dev/c/inRN8tI49O0

Part 1: local/session storage
Part 2: indexeddb
Part 3: web locks
Part 4: cache storage
Part 5: origin private file system
Part 6: quota
Part 7: blob storage
Part 8: broadcast channel
Part 9: shared worker

Bug: 1484966
Change-Id: If2572aed6d332bf992c50caf530368f368d63b2a
Reviewed-on: https://chromium-review.googlesource.com/5025234
WPT-Export-Revision: cc0645dfde8abc75deb4a684439bc36effa454fb

PR 43118 applied with additional changes from upstream: 16b940fe64c0555ccd238f7775f972c20ebe8ff1, f8a2bb02f125b7733df4dc4f9b5d9cf8ab8ba344, ec7b0461b88da855e02ce6bbfa9fd4e4639283d8, edffd95f5be7de49876918e25dfcbbb139054711, f4014fc03513a582e3e01b76607f072971cf5183, 5a2e2a896687b1e5493b16093ccb6a0d3e56c209, e22f2ccdad7a2a1b073672f5a592cacdc6a34178
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
Whiteboard: [wptsync downstream error] → [wptsync downstream]
You need to log in before you can comment on or make changes to this bug.