Text Area for Customizable Options shows line break html<br/> on the front end in cart area if a user enters more than 55 characters

[adamstapley]

Summary of the issue
We have Customizable Options with text areas where people can enter up to 350 characters. If they enter a message that's 50 characters with line breaks it all works OK and displays properly in the cart area. If they enter more than 55 characters the cart area displays the html
line break code

Preconditions (*)

Information on your environment
Running Magento 2.4.2
Dedicated server
PHP 7.3
MariaDB10.3

Steps to reproduce (*)

Steps to reproduce
Create a product in admin, create two customizable options both with text area option with 350 characters allowed. Enter less than 55 characters in one text area and more than 55 in the other both with spaces and line breaks. Add the item to your cart and you will see the html line breaks in the text area option with more than 55 characters.

Expected result (*)

Cart should just show the text entered in each option and not the html line break code

Actual result (*)

Cart shows html in option

[m2-assistant]

Hi @adamstapley. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

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

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, 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

[adamstapley]

@magento give me 2.4-develop instance - upcoming 2.4.x release

[magento-deployment-service]

Hi @adamstapley. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @adamstapley, here is your Magento Instance: https://b8f5c5bbfe16193694e9c15ef90cc1d9-2-4-develop.instances.magento-community.engineering
Admin access: https://b8f5c5bbfe16193694e9c15ef90cc1d9-2-4-develop.instances.magento-community.engineering/admin_4757
Login: 08f98572
Password: ef563a8dae6a

[adamstapley]

Created a test product and issue still exist. This is a bundle product
URL: https://b8f5c5bbfe16193694e9c15ef90cc1d9-2-4-develop.instances.magento-community.engineering/checkout/cart/configure/id/5/product_id/2047/

[adamstapley]

This looks like it might be related to issue #25418

I created a fix in Magento 2.4.2:
/public_html/vendor/magento/module-checkout/view/frontend/templates/cart/item/default.phtml

Line 52

escapeHtml($_formatedOptionValue['full_view']) ?>

Change to

escapeHtml($_formatedOptionValue['full_view'], ['span', 'a']) ?>

All line break code is removed. I presume this isn't the 100% correct way to achieve this but it works for me at the moment and I'm not a developer :)

[m2-assistant]

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

[adamstapley]

Reproduced on 2.4.x.

[m2-assistant]

Hi @Den4ik. 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.

[AZiniukhin]

@magento I am working on this

[magento-engcom-team]

✅ Confirmed by @engcom-Alfa
Thank you for verifying the issue. Based on the provided information internal tickets MC-42773 were created

Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[gabrieldagama]

Hi @adamstapley. Thank you for your report.
The issue has been fixed in #33256 by @AZiniukhin in 2.4-develop branch
Related commit(s):

• f724fece9f6704af67ca2a14ffe3c8d5adf38e7e
• a3bf2977c53b96de2a5ab271624b90a7ec4dcac1
• b506bb4a357b53c35176ca9e175de53144110623

The fix will be available with the upcoming 2.4.3 release.