-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Labels
Area: AccountComponent: CustomerIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: P2A defect with this priority could have functionality issues which are not to expectations.A defect with this priority could have functionality issues which are not to expectations.Progress: doneReported on 2.4.1Indicates original Magento version for the Issue report.Indicates original Magento version for the Issue report.Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchThe issue has been reproduced on latest 2.4-develop branchSeverity: S3Affects non-critical data or functionality and does not force users to employ a workaround.Affects non-critical data or functionality and does not force users to employ a workaround.
Description
Originally this issue was reported in 5983e17#commitcomment-44080850 by @HenKun.
The following commit 5983e17 leads to similar issues described in #24847.
Preconditions (*)
- Magento 2.4.1, or 2.4-develop
Steps to reproduce (*)
- Add the following code to the page on frontend:
<script>
require(['Magento_Customer/js/customer-data'], function (customerData) {
console.log(customerData.getExpiredSectionNames());
});
</script>
- Go to the frontend, see the console
Expected result (*)
Actual result (*)
Additional info from Engcom
Add the script to, for example, /app/code/Magento/Customer/view/frontend/templates/form/edit.phtml
- In the Storefront, Sign In as a Customer
- Go to My Account
- Click Edit under Contact Information
- Observe the dev console
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.
- 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”.
mrtuvn, HenKun, pitbulk and novikormrtuvn and pitbulk
Metadata
Metadata
Assignees
Labels
Area: AccountComponent: CustomerIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: P2A defect with this priority could have functionality issues which are not to expectations.A defect with this priority could have functionality issues which are not to expectations.Progress: doneReported on 2.4.1Indicates original Magento version for the Issue report.Indicates original Magento version for the Issue report.Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchThe issue has been reproduced on latest 2.4-develop branchSeverity: S3Affects non-critical data or functionality and does not force users to employ a workaround.Affects non-critical data or functionality and does not force users to employ a workaround.
Type
Projects
Status
Done