Page Builder breaks page when content with Emoji is saved

[ganeddact]

Preconditions and environment

• Magento version: 2.4.7-p4
• Database collation is utf8_mb4_general_ci
• Just add a new page or save an existing one, by adding an emoji

Steps to reproduce

1. Add a new page or edit an existing one, using Page Builder
2. Make the page with several rows
3. add/paste the emoji in a text content, be sure it is not in the last element row (to see the effects to the rest of the page after save)
4. save

Expected result

Page saves correctly, and works again when reopen for edit

Actual result

• From the emoji onwards, the page gets entirely cut (check database value, page is cut exactly where the emoji should be and the rest of the page is missing).
• JS error showing "TypeError: Cannot read properties of null (reading 'setAttribute')"
• Page Builder stops working, making the page not editable anymore
• if I wrap line 51-53 of vendor/magento/module-page-builder/view/adminhtml/web/js/stage-builder.js with a check if(element !== null), at least I'm able to salvage the rest of the page, but all that was after the emoji is lost

Additional information

No response

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 @ganeddact. 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.

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

[ganeddact]

@magento I am working on this

[m2-assistant]

Hi @ganeddact! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

[ganeddact]

@magento add to contributors team

[m2-assistant]

Hi @ganeddact! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

[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

  - 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.

[ganeddact]

@magento I am working on this

[ganeddact]

@magento give me 2.4-develop instance

[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).
• 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

  - 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]

Hello @ganeddact ,

We appreciate your report and collaboration.

We attempted to reproduce this issue, but using the steps that were given, we were unable reproduce it. Please provide us a screenshot, description, and more information so we can replicate. Refer to the screenshot for the references.

Therefore, this issue is tagged as Needs update.

Thank you