tree 7e3b372e6403713f55df3f5b95a6cd83ce96c425
parent b7a510ac4902cad0d4077f67c106bed3afad0965
author Ari Chivukula <arichiv@chromium.org> 1674624899 +0000
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> 1674624899 +0000

[StorageKey] Allow (de)serialization of opaque top_level_site

It's possible, for example on a data url with an iframe, to have a
non-opaque origin and an opaque top_level_site. In such instances we
need to be able to serialize the opaque top_level_site so that storage
access is possible. In future, we may want to remove this capability but
with a target launch of M112 we cannot take on more near term
deprecations.

Bug: 1407243
Change-Id: I0698e0b209884571e9c24b0f3b54490de90d3a2b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4189064
Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Commit-Queue: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Auto-Submit: Ari Chivukula <arichiv@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Steven Bingler <bingler@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1096631}