-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Chromium storage partitioning compatible with Brave ephemeral storage implementation #26165
Comments
Thanks @goodov 👍 Work to support |
@goodov should this be checked on Android as well - or is there a separate issue for implementation on Android? |
This issue also covers Android and it should be tested as well. |
Verified with
Per #26165 (comment), running through the tests under
Also ran through the test under
Note, per #26165 (comment), no need to run these tests with Ephemeral Storage disabled. |
@goodov two questions for you:
Thanks! |
That doesn't look right. Did you enable cookies globally on
No, please stop doing that. I'll update the test page to remove this text. We should not test the disabled stage at this point as it's an always-on feature. |
Verified on
STEPS:
ACTUAL RESULTS:
Galaxy Tab S8 / Tablet |
Verification
|
Chromium has been working on its own storage partitioning for a while, they've come up with
StorageKey
that is spread across many storage APIs. The structure is similar toNetworkIsolationKey/NetworkAnonymizationKey
, but is used mostly for eTLD+1 partitioning of cross sites (relative to the top origin).We should adopt
StorageKey
as much as possible, befriend it with our ephemeral storage implementation and enable upstream partitioning where possible. Some of our partitioning tasks (for ex. #24712) can useStorageKey
for simpler implementation.Here's Chromium invite to test their partitioning in the wild: https://developer.chrome.com/en/blog/storage-partitioning-dev-trial/
The text was updated successfully, but these errors were encountered: