Uncaught Error: Script error for: [...] http://requirejs.org/docs/errors.html#scripterror [Firefox]

[Karol-Aniszewski]

Preconditions (*)

The issue can be reproduced on

1. Firefox (99.0.1 (64-bit))
2. Magento ver. 2.4.3 .
3. https://demo-magento-2.auroracreation.com/pl/women.html

Steps to reproduce (*)

1. Go to Magento Home Page using Firefox
2. Go to one of the main categories
3. Before a page stops loading go to another of the main categories

• it should work even without login to any customer account
• this issue doesn't appear on Chrome
• the error message is like: Uncaught Error: Script error for: [...] http://requirejs.org/docs/errors.html#scripterror In the square brackets there are different JS files applied by RequireJS.

Expected result (*)

There should be no errors in console on Firefox 99

Actual result (*)

1. Multiple errors in console
2. Screenshot

---

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 with no 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.
• [x] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @Karol-Aniszewski. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

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

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.

:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

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

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant[bot]]

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: :point_down:

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

[engcom-November]

Verified the issue on both Firefox and Chrome Browsers using Magento 2.4-develop and the issue is reproducible on Firefox browser but not on chrome browser. Hence confirming the issue.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.magento.com/browse/AC-2940 is successfully created for this GitHub issue.

[m2-assistant[bot]]

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

[blacktek]

Hello, is there any update on this issue?

We still see the issue happening on 2.4.3 version.

Thank you

[sanganinamrata]

I'm also facing the same issue on Magento version 2.4.1. Any updates on this?

[RedSign77]

Hi! We are also facing this issue on 2.4.4-p2. Any update of this?

[onlinebizsoft]

I think it is something to do with how RequireJS load and handle errors while loading. I believe this should happen for all browsers and all Magento versions. Not sure if anyone had a solution, they are not bug but very annoying and make very hard to track real errors

[AndresInSpace]

Can I get some clarification here: Is anything actually breaking when this shows in console for any of you??

This seems like an issue with Firefox polluting console because it is letting thread continue during the process of unloading old page and loading new page.

Add timestamps to your console logs, compare to network events and when the new page document actually is received.

I think this should be closed if confirmed and raised to firefox as a separate issue.

[blacktek]

Hello, I'll be out of office until the 6th of September. I'll reply on my return.

Kind Regards, TT

[engcom-Bravo]

HI @Karol-Aniszewski,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance with firefox browser and we are not able to reproduce the issue.kindly refer the screenshots.

There were no errors in console on Firefox browser.

Hence we are closing this issue.

Thanks.