Console errors breaking Admin Stores Configuration on 2.4.7-p3

[dphilipps]

Preconditions and environment

-2.4.7-p3 fresh install
DEVELOPER MODE
(Also occurs in Production mode but much less frequently - can take 5 mins of clicking around)

This happens inconsistently, browsing around number of different admin sections is needed before the console errors are displayed. It isn't one section which conistently breaks.

Steps to reproduce

1. In admin browse to Stores->Configuration
2. Open console
3. Click between sections within areas on left menu such as General->Web, General->Currency Setup, Customers->Customer Configuration etc.
4. Look for console error then attempt to open a section on the right

Expected result

Drop-down sections in admin should expandable by clicking down arrow.
No console errors are expected

Actual result

Drop-down sections in admin CANNOT be expanded by clicking down arrow.

Uncaught TypeError: ah.attachEvent is not a function at s (legacy-build.min.js:12:31254)

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

[dphilipps]

@magento give me 2.4.7-p3 instance

[dphilipps]

@magento give me 2.4.7 instance

[dphilipps]

@magento I am working on this

[dphilipps]

@magento give me 2.4.7-p3 instance

[dphilipps]

@magento give me 2.4-develop instance

[dphilipps]

Is Magento instance deployment not working?

[mflott]

I'm also seeing this issue quite frequently, same Magento version.

Including the error message in the description, I'm also often seeing this on the occasion that it breaks:

Uncaught TypeError: $(...).filter(...).collapse is not a function
    at HTMLDivElement.<anonymous> (VM22992 theme.js:629:12)
    at Function.each (VM22991 jquery.js:383:35)
    at VM22992 theme.js:626:7
    at Object.execCb (require.js:1720:33)
    at Module.check (require.js:893:51)
    at Module.<anonymous> (require.js:1153:34)
    at require.js:138:23
    at require.js:1205:21
    at each (require.js:62:31)
    at Module.emit (require.js:1204:17)

[mflott]

Related issue: #39066

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