fix: Same-origin iframe set/get cookie/localStorage bug #600
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
SarahJane87
changed the title
gioboa
approved these changes
Jun 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is it?
Description
Bug: Unable to get/set localStorage/cookies in a same-origin iframe created with Partytown.
Expected: Able to get/set localStorage/cookies in a same-origin iframe created with Partytown.
Fix: Set isSameOrigin after iframe src is set
Use cases and why
"Partytown unable to get cross-origin localStorage" warning from Pinterest tracking pixel even though iframe src
https://ct.pinterest.com/ct.htmlis proxied.Checklist: