Skip to content
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

Add top-level site to storage key. (#127) #144

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

wanderview
Copy link
Member

@wanderview wanderview commented Jun 2, 2022

  • At least two implementers are interested (and none opposed):
  • Tests are written and can be reviewed and commented upon at:
  • Implementation bugs are filed:
    • Chrome: …
    • Firefox: …
    • Safari: …

(See WHATWG Working Mode: Changes for more details.)


Preview | Diff

storage.bs Outdated Show resolved Hide resolved
storage.bs Outdated Show resolved Hide resolved
storage.bs Outdated Show resolved Hide resolved
@wanderview
Copy link
Member Author

Its unclear to me if this PR is something we are comfortable merging into the spec now or not. Do we have adequate consensus on using top-level site for partitioning? My sense is we have at least two engines between chromium and gecko, but there are still some differences to webkit (ephemeral 3rd party storage).

@annevk
Copy link
Member

annevk commented Jun 9, 2022

I think that only affects how long the storage is kept, not how it's keyed, right?

It seems to me that all browsers want to align on this keying.

cc @johnwilander @cdumez

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants