-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade jquery to 3.6.0 #34162
Upgrade jquery to 3.6.0 #34162
Conversation
Hi @mrtuvn. Thank you for your contribution
❗ Automated tests can be triggered manually with an appropriate comment:
You can find more information about the builds here ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review. For more details, please, review the Magento Contributor Guide documentation. 🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket. 🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
44486db
to
7389462
Compare
remain task upgrade jquery ui (current latest 1.12.1) following magento seperate to modules |
Hi @mrtuvn ! |
@mrtuvn Let me share some info: We(magento team) are working on jquery-ui upgrade. Please contact me if you plan to work on jquery-ui upgrade so we can sync and avoid duplication in efforts |
Hi @xmav you can work directly on this branch . If you need write access branch please let me know. |
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
@xmav Can you deliver this error note to team |
Hi @mrtuvn |
Upgrade to jquery 3.6.0 + jquery ui to latest -> Go to admin |
Got it. We are currently working on jqueryUI only so we don't see this error yet |
@magento run Unit Tests, Functional Tests EE, Functional Tests CE, Functional Tests B2B |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
ce9a913
to
47dbe8c
Compare
@krissyhiserote i will let this PR like this. Other fixes can do by another seperate PR. So you team can keep working as normal. Later code merge to develop i will sync with this. Seem a long road ahead for check new compatible |
Afternoon all, Our Penetration testers have found that the current jQuery version used in Magento 2.4.3 is vulnerable in some means to hackers does this thread relate to the issue found? |
2.4.3 still use old version jquery. This pr will update to higher version. Internal team currently working upgrade compatible with new update |
@mrtuvn thanks for letting me know, when you say internal team do you mean the guys working at Magento? |
Yes @xmav may know more details |
Hi there, @mrtuvn . If you get a chance, could you help me understand the reason for changes to |
That file apply fixes for lighthouse warn "Does not use passive listeners to improve scrolling performance" |
…o upgrade-jquery-3.6.0
Pull latest code to branch |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
@mrtuvn I don't think that lighthouse warnings are necessary to fix for this upgrade. The upgrade does not cause these issues correct? This change to patches breaks our unit tests since the function signature for the callback in the patch is not valid. (ns is null) We will create a separate ticket to track and investigate this. |
I can remove that file in this scope of ticket. And tracking warning lighthouse in seperate PR/ticket |
@magento run Functional Tests CE, Functional Tests EE, Functional Tests B2B, Unit Tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
Deleted file patches jquery. |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
Revert changes to avoid conflicts
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
Closed this because internal team already delivery updated jquery 3.6.0 to mainline codebase (2.4-develop branch) |
good morning @mrtuvn thanks for keeping us updated, when will the upgraded Jquery be available to upgrade on M 2.4.3 |
I am not aware of plans to backport this to 2.4.3 |
Good Luck :) I tried it years ago. |
Description (*)
This pull efforts to upgrade jquery to version 3.6.0
added resolve passive event listeners problem on mobile (touchstart) when call preventDefault
https://cdn.jsdelivr.net/npm/jquery@3.6.0/dist/jquery.js
minify version
https://cdn.jsdelivr.net/npm/jquery@3.6.0/dist/jquery.min.js
jquery-migrate 3.3.2
https://code.jquery.com/jquery-migrate-3.3.2.js
Guide
https://jquery.com/upgrade-guide/3.0/
Remain works
-remove old patches (jQuery UI - v1.12.1)
https://github.com/magento/magento2/tree/2.4-develop/lib/web/jquery/patches
seperate each components to individual package
-check compatible with remain widgets
https://github.com/magento/magento2/tree/2.4-develop/lib/web/jquery (Main here)
Other places in external modules, EE, v.v
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
Should we minimal jquery widget ?
'jquery-ui-modules/core',
'jquery-ui-modules/accordion',
'jquery-ui-modules/button',
'jquery-ui-modules/datepicker',
'jquery-ui-modules/dialog',
'jquery-ui-modules/draggable',
'jquery-ui-modules/effect',
'jquery-ui-modules/menu',
'jquery-ui-modules/mouse',
'jquery-ui-modules/position',
'jquery-ui-modules/progressbar',
'jquery-ui-modules/resizable',
'jquery-ui-modules/selectable',
'jquery-ui-modules/slider',
'jquery-ui-modules/sortable',
'jquery-ui-modules/tabs',
'jquery-ui-modules/timepicker',
'jquery-ui-modules/tooltip',
'jquery-ui-modules/widget'
Instead load all above. We only use on demands files
Contribution checklist (*)