JS Code is rendered as text for the billing address's street

[cdcrothers]

Preconditions and environment

• Magento version 2.4.2-p2 Enterprise and Community
• Enable google/analytics/active

#25684 (comment)
#26276 (comment)
^ relevant issues that reported and caused the bug.

Steps to reproduce

Reach billing step.
See billing address's street render JS code on the frontend.

Expected result

Billing address renders normally.

Actual result

Billing address renders JS code on frontent

Additional information

Short term patch/solution is the apply the patch seen in the other issue's comment linked in the description.

Root cause boils down to some namespacing issues and very poor practices within Array prototype modifications made by prototype.js. The prototype lib has been unsupported for 7+ years. The long term solution would be to remove frontend/luma dependencies on prototype.js.

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 @cdcrothers. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-November. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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-November]

Hi @cdcrothers ,
Thank you for reporting and collaboration. Verified the issue on Magento 2.4-develop with enterprise edition modules enabled but the issue is not reproducible with below steps performed:
Steps performed:

1. Configured Google Analytics Account by creating account with property
2. Copy Measurement ID - Login to Magento admin - Stores - Configuration - Sales - Google API - Enabled and selected Account Type - Google Analytics4, add measurement id and save
3. Cache clean
4. Front end - Place Order - No issue: No errors observed in console and order placed successfully.
5. Created Google tag Manager account and noted container id
6. Import container (Admin - Container - import container)
7. Login to Magento admin - Stores - Configuration - Sales - Google API - Select Account Type Google GTag , enter container add and save
8. Navigate to Content - Design - Configuration - HTML Head section - added the GTM script setup
9. In the footer section also added the GTM code and save configuration
10. Clear cache
11. Front end - Place Order - No issue. Order placed successfully with no errors.
    Kindly recheck the issue on Magento 2.4-develop with enterprise edition and provide missing steps if any if the issue is still reproducible.
    Thank you.
    
    

[engcom-November]

Hi @cdcrothers ,
We are closing this issue as there has been no latest update on the same. Kindly reopen / create new issue if you are still facing any issues.
Thank you.