Skip to content
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 jquery deprecations #1786

Closed
wants to merge 26 commits into from
Closed

Fix jquery deprecations #1786

wants to merge 26 commits into from

Conversation

venkatraj
Copy link

Reference Issues/PRs

None

What does this implement/fix? Explain your changes

Fixing the JQuery deprecation code

Any other comments?

No

@vitality82
Copy link

Are there plans to merge this PR? I'm upgrading a legacy app using tablesorter to jQuery 3.6 and getting lots of migration warnings that this PR is about to solve.

@Alexandermjos
Copy link

Any updates on this? I am also upgrading legacy app 🤣

@marcos-castrillo
Copy link

Same situation here

@Mottie
Copy link
Owner

Mottie commented Feb 3, 2022

I'll look into this over the weekend. Thanks for your patience.

@Mottie
Copy link
Owner

Mottie commented Feb 7, 2022

Sorry, this is taking longer than I thought... so much stuff to update!

@marcos-castrillo
Copy link

Thanks for taking care of this!

@elebitzero
Copy link

$.trim is another deprecated function that is not migrated in the PR yet.

$.trim has been deprecated in jQuery 3.5; please use the native String.prototype.trim method instead. Unlike jQuery.trim, String.prototype.trim does not work with types other than strings (null, undefined, Number). Make sure that your code is compatible when migrating.

@nagyimre1980
Copy link

nagyimre1980 commented Sep 6, 2022

pls..... new verison... thx

@venkatraj venkatraj closed this by deleting the head repository Jan 19, 2023
@nagyimre1980
Copy link

pls..... new verison... thx

@nagyimre1980
Copy link

deleting?? :(

@venkatraj
Copy link
Author

@nagyimre1980 Sorry, we need to ship those changes in our software. All third party libraries are forked in our company account. Since I can't fork same repo from two places, I have to delete this, in order to fork our company repo and merge the changes.

May be our Lead Developer will create a PR with those changes.

@nagyimre1980
Copy link

NEW PR?

@rylanb
Copy link

rylanb commented May 26, 2023

Please do consider this, I don't want to go in and update the library for the bind/unbind/trim deprecation warnings I've been getting for months. Thank you if you can get to this! Thanks for the plugin, as well!

@DavidAnderson684
Copy link

This fork has the jQuery compatibility commits in it: https://github.com/DavidAnderson684/tablesorter/tree/master . If anyone wants to create a new PR on https://github.com/Mottie/tablesorter/ using those changes, then they are welcome.

@AviHafner
Copy link

Hi @DavidAnderson684
On this site there are 2 customized files https://www.admin.technion.ac.il/tablesorter-V3.1/
this version working with Jquery 4
its taking from version of tablesorter Version 2.31.3
I would be very happy if you adopt the changes in this version and make them official.

@DavidAnderson684
Copy link

@AviHafner You're confusing me with someone else, I am not a committer for Mottie/tablesorter.

jeffwidman added a commit to pallets-eco/flask-debugtoolbar that referenced this pull request Apr 11, 2024
Ths is a follow-on PR to
#241 in order to
fix the deprecation warnings:
* `bind()` replaced by `on()`
* `click(handler)` replaced by `on('click', handler)`

Three deprecation warnings remain, but they are caused by the
`jquery.tablesorter.js` plugin, so need to be handled upstream.

Related:
* Mottie/tablesorter#1786
* #166
jeffwidman added a commit to pallets-eco/flask-debugtoolbar that referenced this pull request Apr 11, 2024
Ths is a follow-on PR to
#241 in order to
fix the deprecation warnings:
* `bind()` replaced by `on()`
* `click(handler)` replaced by `on('click', handler)`

Three deprecation warnings remain, but they are caused by the
`jquery.tablesorter.js` plugin, so need to be handled upstream:
* Mottie/tablesorter#1787
* Mottie/tablesorter#1786

Related:
* #166
jeffwidman added a commit to pallets-eco/flask-debugtoolbar that referenced this pull request Apr 13, 2024
Ths is a follow-on PR to
#241 in order to
fix the deprecation warnings:
* `bind()` replaced by `on()`
* `click(handler)` replaced by `on('click', handler)`

Three deprecation warnings remain, but they are caused by the
`jquery.tablesorter.js` plugin, so need to be handled upstream:
* Mottie/tablesorter#1787
* Mottie/tablesorter#1786

Related:
* #166
jeffwidman added a commit to pallets-eco/flask-debugtoolbar that referenced this pull request Apr 13, 2024
Ths is a follow-on PR to
#241 in order to fix the deprecation warnings:
* `bind()` replaced by `on()`
* `click(handler)` replaced by `on('click', handler)`

Three deprecation warnings remain, but they are caused by the `jquery.tablesorter.js` plugin, so need to be handled upstream:
* Mottie/tablesorter#1787
* Mottie/tablesorter#1786

Related:
* #166
@kczx3
Copy link

kczx3 commented Aug 14, 2024

So far these are all just deprecations however they all would prevent this library from functioning with jQuery 4. I see a second beta release for jQuery 4 was released last month. I don't think it is too farfetched to think that a final release for jQuery 4 could arrive by the end of the year. Seeing that Mottie just committed a change that removes the ie8 option from the gruntfile, it also isn't too crazy to think that this project could be updated to support only IE11. However, the choice would have to be made if the supported jQuery versions could be reduced. Seeing as this project hasn't had much in the way of fixes and enhancements in 4 years, I would support a major version bump that aligns with the move to only jQuery 4+ support. Drastic fixes and enhancements in the future are probably not too likely so requiring folks on older jQuery 3 or less to use the 2.x version of tablesorter seems appropriate to me. They probably won't miss out on much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.