-
Notifications
You must be signed in to change notification settings - Fork 9.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
Prevent cross origin iframe content reading #32244
Conversation
Hi @ihor-sviziev. Thank you for your contribution
❗ Automated tests can be triggered manually with an appropriate comment:
You can find more information about the builds here ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review. For more details, please, review the Magento Contributor Guide documentation. 🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket. 🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
Fix static test
@magento run all tests |
@magento create issue |
@magento run Functional Tests B2B, Functional Tests EE, Static Tests |
2 similar comments
@magento run Functional Tests B2B, Functional Tests EE, Static Tests |
@magento run Functional Tests B2B, Functional Tests EE, Static Tests |
@magento run Functional Tests EE |
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
@magento run Unit Tests, Functional Tests B2B |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅ Approve
Researched and discussed with @ihor-sviziev
Changes make since if $(element)
will be array of 2+ elements. I did't found steps for reproducing issue.
But I admit that element
could be selector string by some external libraries like FB pixel, twitter etc. Moving code block prevent issue.
Hi @Den4ik, thank you for the review.
|
Hi @ihor-sviziev, we also encountered this problem today.
Full patch:
Note: I didn't read the note on your conversation "$(element) will be array of 2+ elements" until now. So it seems to make sense to put this check inside the contents function. (Updated full patch) Could you check this once ? |
Hi @ihor-sviziev, As per this #32264 (comment) We are closing this PR. Please feel free to reopen the PR. Thanks. |
Description (*)
Issue described in #8005, #7914 will message like this reproducing randomly (shown as console error):
Seems like it's happening because domain checking only on the exact element, not on all listed
The message looks like this:
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)
Resolved issues: