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

Change 3p storage handling to improve webcompat #8373

Closed
pes10k opened this issue Feb 23, 2020 · 1 comment
Closed

Change 3p storage handling to improve webcompat #8373

pes10k opened this issue Feb 23, 2020 · 1 comment
Assignees
Labels
privacy privacy-pod Feature work for the Privacy & Web Compatibility pod webcompat/shields Shields is breaking a website.

Comments

@pes10k
Copy link
Contributor

pes10k commented Feb 23, 2020

Currently Brave
1) doesn't send cookies to any sub-requests (excepting hardcoded exceptions), even for eTLD+1
2) doesn't allow any storage in embedded frames
3) nulls out storage related endpoints in embedded frames

All the above will cause webcompat problems.

We should maintain the same privacy protections, but decrease webcompat concerns, by making the following changes:
1) send cookies for eTLD+1 equal requests
2) all eTLD+1 equal frames have standard storage
3) eTLD+1 not-equal frames should have ephemeral (e.g. document length) storage

@pes10k pes10k added webcompat/shields Shields is breaking a website. privacy privacy-pod Feature work for the Privacy & Web Compatibility pod labels Feb 23, 2020
@pes10k
Copy link
Contributor Author

pes10k commented Mar 3, 2020

closed in favor of #8514

@pes10k pes10k closed this as completed Mar 3, 2020
@bbondy bbondy added this to the Closed / Invalid milestone Jun 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
privacy privacy-pod Feature work for the Privacy & Web Compatibility pod webcompat/shields Shields is breaking a website.
Projects
None yet
Development

No branches or pull requests

3 participants