-
Notifications
You must be signed in to change notification settings - Fork 10.7k
Fix/issue 28284 #29044
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
Fix/issue 28284 #29044
Conversation
|
📦 Artifacts ready for download! |
|
I pushed a few commit fixing things I found as I was going through this... I double-checked all of the woocommerce/assets/js/frontend/add-to-cart.js Lines 82 to 84 in dd10ad5
I'm not really sure how to address that in a way that would be backwards-compatible without essentially including the entire part of jQuery Migrate that handles data compatibility. If anybody happens to set data using I gave the JS and PHP files another pass — I want to run through them one more time to make sure that nothing was missed. I also want to give the e2e tests a go with the Test jQuery Update plugin installed to see if they catch anything that I might have missed. |
569985b to
4cd2bad
Compare
08278df to
1701a04
Compare
|
@roykho @jonathansadowski The two source E2E failures are creating shipping methods/zones and order search. Let me know if you'd like me to investigate. |
…g jQuery object; was native JS bind)
1701a04 to
98b4968
Compare
ObliviousHarmony
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the great work here, this was a gargantuan effort.
To test this PR I set up a site locally with the plugin disabling jQuery Migrate. I was able to successfully run the E2E suite. After it passed a few compatibility tests as well, I'm happy to report that this PR looks like it works.
After reviewing the code as well, I'm ready to approve it!
| if(org_title != ""){ | ||
| if(!opts.content){ | ||
| org_elem.removeAttr(opts.attribute); //remove original Attribute | ||
| org_elem.prop(opts.attribute, false); //remove original Attribute |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@roykho I think this is breaking some extensions using jquery-tiptip (see 693-gh-woocommerce/woocommerce-product-addonsr example).
All Submissions:
Changes proposed in this Pull Request:
This PR updates WooCommerce for compatibility with jQuery 3 in preparation of the removal of jQuery Migrate in a future version of WordPress.
closes #28284 #28286
For reference, I am using this documentation here https://jquery.com/upgrade-guide/3.0/ and here https://github.com/jquery/jquery-migrate/blob/master/warnings.md
How to test the changes in this Pull Request:
IMPORTANT NOTE
It is quite difficult or not feasible to test every line changes. You may not even know how or where to try and produce the results. We can only test everything we do know such as critical flows and little tidbits.
There are some gotchas that I've found and will document that here p7bje6-2VM-p2#comment-5896.
Changelog entry