Console error in Email preview in the Magento admin

[bosskar231]

Summary

Preconditions and environment
Getting a console error in all magento environment in version 2.4.6

Steps to reproduce
Fresh Install of M2.4.6 in environment as above
Login to backend

Nav to Admin>Marketing>Email Templates>click preview
Open developer options and you can able to find a error in the console.

Bocked script execution in 'http://localmagento/index.php/admin/admin/email_template/popup/key/53379463b63d4ed7911eaf8d8aa133d7f186826b20ecfbf01cf5d5ec5c8e349f/' because the document's frame is sandboxed and the 'allow-scripts' permission is not set.

Examples

We checked the code and found this phtml under the path

vendor/magento/module-email/view/adminhtml/templates/preview/iframeswitcher.phtml

Proposed solution

<iframe name="preview_iframe"
           id="preview_iframe"
           frameborder="0"
           title="<?= $block->escapeHtmlAttr(__('Preview')) ?>"
           width="100%"
           sandbox="allow-same-origin allow-pointer-lock"
   ></iframe>

In the above code snippet you can find sandbox attribute, In which if we add allow-scripts value with other allow-same-origin and allow-pointer-lock. After adding the allow scripts the console error is not occuring in the preview templates.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @bosskar231. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @bosskar231,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is reproducible. Kindly refer the screenshots.

Steps to reproduce

• Login to backend
• Nav to Admin>Marketing>Email Templates>click preview
• Open developer options and you can able to find a error in the console.

While previewing the email template we are getting the error in the console as below

Blocked script execution in 'http://mgr.local/admin/admin/email_template/popup/key/2bf91b83ae6c6742fafc0c97de840642549ed9540a257f73d5f7c03336fbfd3c/' because the document's frame is sandboxed and the 'allow-scripts' permission is not set.

It is happening for every email template.

Hence Confirming the issue.

Thanks.