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

Have deviceId follow partitioning rules for storage (such as localStorage) #674

Merged
merged 3 commits into from
Apr 2, 2020

Conversation

jan-ivar
Copy link
Member

@jan-ivar jan-ivar commented Apr 2, 2020

Fixes #598. @annevk PTAL.

@jan-ivar jan-ivar self-assigned this Apr 2, 2020
Copy link
Member

@annevk annevk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is reasonable for now. Long term all APIs should build on to-be-defined primitives in https://storage.spec.whatwg.org/ that would give some space to store things.

Iframes that are of the same origin won't have a different partition though as they could just reach the top via script.

@youennf
Copy link
Contributor

youennf commented Apr 2, 2020

Can we refer to https://storage.spec.whatwg.org/ directly then?

@jan-ivar
Copy link
Member Author

jan-ivar commented Apr 2, 2020

We should, but it looks like doing so is blocked on whatwg/storage#18, so I think we should merge this for now and open an issue to come back to it.

@jan-ivar jan-ivar changed the title Have deviceId follow partitioning rules for localStorage. Have deviceId follow partitioning rules for storage (such as localStorage) Apr 2, 2020
@jan-ivar jan-ivar merged commit 8f7d40d into w3c:master Apr 2, 2020
@jan-ivar jan-ivar deleted the partition branch April 2, 2020 15:05
@jan-ivar jan-ivar added the privacy-pr PRs from privacy review label Oct 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
privacy-pr PRs from privacy review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should deviceId be partitioned by top level origin and document origin
3 participants