-
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
Allow cookies in 1st-party iframes nested inside 3rd-party iframes when 3rd-party cookie blocking is enabled #9564
Comments
bridiver
added a commit
to brave/brave-core
that referenced
this issue
Apr 30, 2020
…ns for wp/wordpress and playstation/sonyentertainmentnetwork fix brave/brave-browser#8629 fix brave/brave-browser#9564
32 tasks
bridiver
changed the title
1st-party iframes nested inside 3rd-party iframes have cookies blocked
Cookies are blocked in 1st-party iframes nested inside 3rd-party iframes when 3rd-party cookie blocking is enabled
Apr 30, 2020
diracdeltas
changed the title
Cookies are blocked in 1st-party iframes nested inside 3rd-party iframes when 3rd-party cookie blocking is enabled
allow cookies in 1st-party iframes nested inside 3rd-party iframes when 3rd-party cookie blocking is enabled
Apr 30, 2020
bridiver
added a commit
to brave/brave-core
that referenced
this issue
May 6, 2020
…ns for wp/wordpress and playstation/sonyentertainmentnetwork fix brave/brave-browser#8629 fix brave/brave-browser#9564
4 tasks
This was referenced May 27, 2020
Marking as |
rebron
changed the title
allow cookies in 1st-party iframes nested inside 3rd-party iframes when 3rd-party cookie blocking is enabled
Allow cookies in 1st-party iframes nested inside 3rd-party iframes when 3rd-party cookie blocking is enabled
May 29, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Currently we block storage on eTLD+1 frames, if they're nested in a non eTLD+1 equal frame. Eg in the below:
The example.org iframe would not get storage.
Brave should give storage to eTLD+1 = frames, irregardless of their position in a frame heirachy
The text was updated successfully, but these errors were encountered: