Category description WYSIWYG is empty on non default storeview #38622

thlassche · 2024-04-16T06:45:07Z

Preconditions and environment

Magento version: 2.4.7
Pagebuilder modules disabled

Steps to reproduce

Edit category in the backend on storeview level
Untick the box 'Use default value' next to the category description field WYSWYG editor
Enter a description in the WYSIWYG editor
Save

Expected result

Description is saved and shown in the edit form

Actual result

WYSIWYG editor is empty after load

Additional information

This is due to a change in dom-observer.js in 5b931fe

The return here now exits the loop early, which wasn't the case before, since it was inside a _ function before: 5b931fe#diff-844cfb7b272693bacaa64be3a0fd96a543cc145b478330777c39682cc15b5961R152

Patch that fixes the issue:

Index: src/vendor/magento/module-ui/view/base/web/js/lib/view/utils/dom-observer.js
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/view/base/web/js/lib/view/utils/dom-observer.js b/view/base/web/js/lib/view/utils/dom-observer.js
--- a/view/base/web/js/lib/view/utils/dom-observer.js	
+++ b/view/base/web/js/lib/view/utils/dom-observer.js	(date 1713248057631)
@@ -149,7 +149,7 @@
         _.each(watchers.selectors, function (listeners, selector) {
             for (let data of listeners) {
                 if (!data.ctx.contains(node) || !$(node, data.ctx).is(selector)) {
-                    break;
+                    continue;
                 }
 
                 if (data.type === 'add') {

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

The text was updated successfully, but these errors were encountered:

m2-assistant · 2024-04-16T06:45:10Z

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

thlassche · 2024-04-16T06:49:29Z

Pull request: #38623

m2-assistant · 2024-04-16T10:48:10Z

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 · 2024-04-17T05:44:54Z

Hi @thlassche,

Thank you for reporting and collaboration.

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

Steps to reproduce

Edit category in the backend on storeview level
Untick the box 'Use default value' next to the category description field WYSWYG editor
Enter a description in the WYSIWYG editor
Save

WYSIWYG editor is empty after load.

Hence Confirming the issue.

Thanks.

github-jira-sync-bot · 2024-04-17T06:03:15Z

✅ Jira issue https://jira.corp.adobe.com/browse/AC-11804 is successfully created for this GitHub issue.

m2-assistant · 2024-04-17T06:03:17Z

✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

m2-community-project bot added this to Ready for Confirmation in Issue Confirmation and Triage Board Apr 16, 2024

m2-community-project bot added the Issue: ready for confirmation label Apr 16, 2024

thlassche linked a pull request Apr 16, 2024 that will close this issue

Fix dom observer not calling all listeners (regression) #38623

Open

5 tasks

m2-community-project bot assigned thlassche Apr 16, 2024

m2-community-project bot added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Apr 16, 2024

ihor-sviziev mentioned this issue Apr 16, 2024

Improve product edit page loading speed #37477

Merged

5 tasks

engcom-Bravo added the Reported on 2.4.7 Indicates original Magento version for the Issue report. label Apr 16, 2024

m2-community-project bot added this to Pull Request In Progress in High Priority Backlog Apr 16, 2024

m2-community-project bot removed this from Ready for Confirmation in Issue Confirmation and Triage Board Apr 16, 2024

m2-community-project bot added the Progress: PR in progress label Apr 16, 2024

engcom-Bravo self-assigned this Apr 16, 2024

engcom-Bravo added Area: Catalog Component: Catalog Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Apr 17, 2024

m2-assistant bot unassigned engcom-Bravo Apr 17, 2024

engcom-Bravo removed the Issue: ready for confirmation label Apr 17, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Category description WYSIWYG is empty on non default storeview #38622

Category description WYSIWYG is empty on non default storeview #38622

thlassche commented Apr 16, 2024

m2-assistant bot commented Apr 16, 2024

thlassche commented Apr 16, 2024

m2-assistant bot commented Apr 16, 2024

engcom-Bravo commented Apr 17, 2024

github-jira-sync-bot commented Apr 17, 2024

m2-assistant bot commented Apr 17, 2024

Category description WYSIWYG is empty on non default storeview #38622

Category description WYSIWYG is empty on non default storeview #38622

Comments

thlassche commented Apr 16, 2024

Preconditions and environment

Steps to reproduce

Expected result

Actual result

Additional information

Release note

Triage and priority

m2-assistant bot commented Apr 16, 2024

thlassche commented Apr 16, 2024

m2-assistant bot commented Apr 16, 2024

engcom-Bravo commented Apr 17, 2024

github-jira-sync-bot commented Apr 17, 2024

m2-assistant bot commented Apr 17, 2024