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

Clarify the expectation if pushState() data is covered by Storage Standard #50

Closed
shuangMoz opened this issue Sep 28, 2017 · 2 comments · Fixed by #91
Closed

Clarify the expectation if pushState() data is covered by Storage Standard #50

shuangMoz opened this issue Sep 28, 2017 · 2 comments · Fixed by #91

Comments

@shuangMoz
Copy link
Contributor

It's not clear to me what's the expectation if pushState() data is covered by Storage Standard. Can we clarify that a bit more? Perhaps privacy reason?

@annevk
Copy link
Member

annevk commented Sep 28, 2017

Yeah, the main reason is that data gets cleared together, but it probably doesn't make sense for pushState() data to end up persisted. It only needs to last as long as the session.

@annevk
Copy link
Member

annevk commented May 2, 2020

This should be (re)moved. This can be stored directly on the document (perhaps browsing session) and doesn't have to live longer.

annevk added a commit that referenced this issue May 15, 2020
Also add some folks to the Acknowledgments section for helping with the previous commit.

Closes #50.
annevk added a commit that referenced this issue May 15, 2020
Also add some folks to the Acknowledgments section for helping with the previous commit.

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

Successfully merging a pull request may close this issue.

2 participants