Open m2-assistant[bot] opened 1 month ago
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:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Issue: Confirmed
once verification is complete. Hello @stefanbackor,
Thank you for the report and collaboration!
We are not able to reproduce this on 2.4-develop. With PrototypeJS 1.7.3 we got the expected result:
Please let us know if we are missing something.
Thank you.
@engcom-November legacy-build.min.js
has to be loaded since this is the script which delivers PrototypeJS. Default theme (installation) does not load such file into storefront. Could legacy-build.min.js
be theme dependent?
Searching thru codebase reveals few hacks in regards of Array.from
and uppy
library.
Testing on Admin Backend does have this issue present.
This issue is automatically created based on existing pull request: magento/magento2#38911: Remove
Array.from
polyfill from PrototypeJS 1.7.3 included inlegacy-build.min.js
PrototypeJS v1.7.3 included in
legacy-build.min.js
breaks nativeArray.from
by forcing its own polyfill implementation effectively breaking 3rd party code run on Magento frontend. ISteps to reproduce
Array.from(new Set([1, 2, 3]))
snippet[]
empty arrayExpected output
[1, 2, 3]
Description (*)
Commenting out
Array.from=$A;
fromlegacy-build.min.js
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Steps to reproduce
Array.from(new Set([1, 2, 3]))
snippet[]
empty arrayExpected output
[1, 2, 3]
Questions or comments
Contribution checklist (*)