-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Update js.js DOM text reinterpreted as HTML #38756
Update js.js DOM text reinterpreted as HTML #38756
Conversation
Hi @Shivam7-1. Thank you for your contribution! Add the comment under your pull request to deploy test or vanilla Magento instance:
❗ Automated tests can be triggered manually with an appropriate comment:
Allowed build names are:
You can find more information about the builds here For more details, review the Code Contributions documentation. |
@magento run all tests |
@magento run all tests |
@magento create issue |
Hi @Shivam7-1. Thank you for your contribution!
Allowed build names are:
You can find more information about the builds here For more details, review the Code Contributions documentation. |
@magento run all tests |
Hii @engcom-Charlie , @engcom-Dash @engcom-Bravo and @engcom-Hotel Could You Please Review This PR Thanks & Regards |
Hii @engcom-Charlie , @engcom-Dash @engcom-Bravo and @engcom-Hotel Could You Please Review This PR Thanks & Regards |
@magento run all tests |
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.
Hello @Shivam7-1,
Please let us know the steps to reproduce the actual issue for this PR that has been created.
Thanks
Hii @engcom-Hotel Thanks For Reviewing Here innerText is indeed Preferable over here instead of innerHtml which makes code more safer |
Hii @engcom-Hotel Could You Please Review This again |
Hii @engcom-Hotel @engcom-Bravo @engcom-Dash Thanks For Reviewing PR |
Hello @Shivam7-1, At this stage, no action is required from your side. The PR is currently in the testing bucket and will be progressed based on priority. We appreciate your patience. Thanks |
Hii @engcom-Hotel Thanks For Reply Could You Ping anyone from Team for Testing Thanks |
Hii @engcom-Hotel @engcom-Charlie @engcom-Bravo Could you Please ping tester here for tasting and get merge this PR So it will get merge Soon |
Hi @Shivam7-1, Thank you for your contribution! Currently team is working on other priority tasks. We will pick this PR for further activities as per the priority. Thank you! |
Hii @engcom-Hotel Thanks For Response |
Hii @engcom-Charlie have you assign this PR for Testing? |
Hii @engcom-Hotel @engcom-Charlie @engcom-Bravo @engcom-Dash Could Team Ping anyone from Team for Testing Thanks |
@magento run all tests |
Hii @engcom-Charlie Is there any update on above test ? |
Hi @Shivam7-1, Thanks for the collaboration & contribution! ✔️ QA PassedPreconditions:
![]() Steps to reproduce
Before: ✖️ ![]() After: ✔️ ![]() Builds are failing, hence, moving this PR to Extended Testing to look into it. Thanks. |
@magento run all tests |
Hii @engcom-Charlie Is there any update on above test ? |
@magento run all tests |
Hi @Shivam7-1, As mentioned here, we are looking into the build test failures. Currently no action is required from your side. We will let you know if its needed. Thank you! |
@magento run Functional Tests B2B, Functional Tests CE, Functional Tests EE, Integration Tests |
Some of the Functional CE test failures are not consistent in recent 2 builds and the consistent once are the known issues.Neither they are failing because of this PR nor part of this PR. ![]() ![]() Known issues: |
Some of the Functional B2B test failures are not consistent in recent 2 builds and the consistent once are the known issues. Neither they are failing because of this PR nor part of this PR. ![]() ![]() Known issues: |
Some of the Functional EE test failures are not consistent in recent 2 builds and the consistent once are the known issues. Neither they are failing because of this PR nor part of this PR. ![]() ![]() Known issues: |
The Integration test failures are consistent in recent 2 builds and they are the known issues. Neither they are failing because of this PR nor part of this PR. Hence moving this PR to Merge in Progress. ![]() ![]() Known issues: |
Hii @engcom-Charlie just for confirmation is this PR is Ready to merge or anything is required from my side? |
Hii @engcom-Charlie @engcom-Hotel @engcom-Dash any update on this PR regarding merging related ? |
Hi @Shivam7-1, As mentioned here, we will let you know if anything is required from your side. We are working on priority work now, will take care of this PR's merging activity as per the priority. |
cb6121a
into
magento:2.4-develop
Description (*)
By using innerText, it will avoid the risk of HTML injection, as these properties automatically escape any HTML special characters in the provided text. This helps prevent cross-site scripting (XSS) vulnerabilities by treating the input as plain text rather than interpreted HTML.
Contribution checklist (*)
Resolved issues: