Response title
This is preview!
Move this topic
JQMIGRATE ALERT: jQuery.expr.filters is now jQuery.expr.pseudos
Solved
- Need more info
- Not a problem
- Temporary fix
- Analyzing
- Working on it
- Solved
in Developing jQuery UI
•
6 years ago
JQMIGRATE ALERT: jQuery.expr.filters is now jQuery.expr.pseudos
jquery-ui.js:2223
if ( $.expr && $.expr.filters && $.expr.filters.animated ) {
jquery-ui.js:2223
if ( $.expr && $.expr.filters && $.expr.filters.animated ) {
1
Replies(21)
The current jQuery UI does not require JQMIGRATE. The warning is probably for another bit of code.
jquery-ui.js:2223 is a different bit in the current jQuery UI.
jquery-ui.js:2223 is a different bit in the current jQuery UI.
Can you provide a demo of your page that shows this warning? Which versions of everything are you using?
JΛ̊KE
Leave a comment on jakecigar's reply
I'm seeing this msg too, running UI 1.12.1 and jQuery 3.1.1.
Is UI 1.12.1 intended to be compatible with 3.1.1? Or should I pull jQuery back to 3.1.0, the officially supported version?
Is there a plan for official 3.1.1 support?
Thanks.
Leave a comment on sparkpool's reply
JQMIGRATE is a tool.
- Install it on your page,
- see the warnings and errors,
- fix them,
- remove it.
If you don’t want to see the warnings, stick with the older, recommended versions, and don’t use JQMIGRATE.
JΛ̊KE
Leave a comment on jakecigar's reply
Thanks, but if I understand the msg correctly, it's code in UI that's causing this, not my code I can look into fixing.
I thought in general, x.x.x releases shouldn't break compatibility, so if it works with 3.1.0 it should work w 3.1.1 also, which is why I asked if these versions are thought to be compatible.
I also don't see 3.1.1 compatibility on the UI roadmap, another reason I wondered if it was already supposed to be compatible, so there might not be any reason to go back to 3.1.0.
Thanks again for your help.
Leave a comment on sparkpool's reply
If you would like to make a tiny demo page, we can take a look. It is difficult to tell which script is making JQMigrate complain.
There is no good reason to jump ahead on jQuery core when the library you are using does not yet support it.
I still start UI projects with 3.1.0 (not 3.1.1)
JΛ̊KE
Leave a comment on jakecigar's reply
I thought in general, x.x.x releases shouldn't break compatibility, so if it works with 3.1.0 it should work w 3.1.1 also, which is why I asked if these versions are thought to be compatible.
Leave a comment on scott.gonzalez's reply
Thanks guys. I'm not complaining, not criticizing anyone or anything, or sounding big alarms, just trying to understand what versions of these libs to use.
I'm updating an old but previously functioning app. Grabbed the latest jQuery because it was the latest. In retrospect I should have checked compatibility with UI first, but I didn't.
Then I got the latest UI, saw that it didn't list latest jQuery, but as I said, thought it should be compatible anyway, wanted to know if I'd gotten that wrong.
I'm updating an old but previously functioning app. Grabbed the latest jQuery because it was the latest. In retrospect I should have checked compatibility with UI first, but I didn't.
Then I got the latest UI, saw that it didn't list latest jQuery, but as I said, thought it should be compatible anyway, wanted to know if I'd gotten that wrong.
Then I got the latest UI, saw that it didn't list latest jQuery
"I thought in general, x.x.x releases shouldn't break compatibility, so if it works with 3.1.0 it should work w 3.1.1 also, which is why I asked if these versions are thought to be compatible. "
I don't have the gift of future cognition Nor do I think do any of the members of the jQuery team.
It is only prudent to assume that when a dependent library is updated, there CAN be incompatibilities with libraries or other code that consumes it - regardless of intent.
If there is a test suite (and in this case there is) compatibility should be considered in question until the test suite has been run on the combo. And, even then, one needs to consider there might be edge cases that have not been previously discovered.
Scott (and the jQuery UI home page seem to be saying that, yes, jquery latest (3.1.1) is indeed compatible with JQUI 1.12.1. (The home page doesn't mention the jQuery version explicitly, only stating "1.7+".)
Scott, can you clarify? As well, it would be useful to know the testing policy. When an updated jQuery is released, which, if any libraries which depend on it are then tested? (most interested here in JQUI and JQM). Is any such testing a part of the formal release procedure for jQuery?
And, of course, of practical necessity, third-party libraries are on their own to test when a new jQuery is released. Regardless of intent, a developer should not presume compatibility with a third-party library until that third-party library has been tested.
IMO, stating "latest" or "x.x+" in documentation is poor practice. Now users have to check the freshness date of the documentation.
In any case, we have two separate issues here: jQuery/JQUI version compatibility. And some warning messages from jQuery Migrate which can in any case be ignored, as a warning is, after all, just a warning.
Leave a comment on sparkpool's reply
I don't know what you want me to clarify. 1.7+ clearly includes 3.1.1.
jQuery UI is tested against the current build of jQuery's master branch on a daily basis. I cannot speak to jQuery's release process as it pertains to the state of other projects' test suites.
There is absolutely no need for anyone to check the "freshness" of our documentation. The support is clearly stated as jQuery 1.7+. If any version of jQuery meets that condition and causes problems with jQuery UI, that is a bug in jQuery UI.
Leave a comment on scott.gonzalez's reply
"I don't know what you want me to clarify."
What you clarified below. Thanks!
------"1.7+ clearly includes 3.1.1.jQuery UI is tested against the current build of jQuery's master branch on a daily basis. I cannot speak to jQuery's release process as it pertains to the state of other projects' test suites.There is absolutely no need for anyone to check the "freshness" of our documentation. The support is clearly stated as jQuery 1.7+. If any version of jQuery meets that condition and causes problems with jQuery UI, that is a bug in jQuery UI."
OP, though, seems to make a imprudent and unwise assumption - that one can rely on version numbering scheme of an included library to insure compatibility with an including library. One cannot. One has to look at testing and experience with the combo. The version numbering scheme only indicates intent and belief. The jQuery team obviously cannot test hundreds of third-party libraries to see if some unknown issue has been created.
For JQUI, it's clear now there is a procedure in place for testing when jQuery is updated.
For any third party libraries, one has to look to the third-party library for this. A version numbering scheme is helpful, but is not prudent to rely on solely.
Leave a comment on watusiware's reply
Hmmm, now I can't find any place where UI is listed as compatible with jQuery 3.1.0 specifically. I really thought I saw that somewhere, but it's not worth chasing further.
So it seems the bottom line is that UI 1.12.1 actually IS thought to be compatible with jQuery 3.1.1, Migrate warnings or not. Since that's the case, I see no reason to stay at 3.1.0 for my project. If problems appear that seem related, it's easy enough to drop back to 3.1.0 and see if that resolves them.
As for the suggestion that "One has to look at testing and experience with the combo", I know of no more likely thorough or reliable source for that experience than the UI project itself, so I'll defer to them.
Thanks again to all for their input, and apologies for the thrash.
So it seems the bottom line is that UI 1.12.1 actually IS thought to be compatible with jQuery 3.1.1, Migrate warnings or not. Since that's the case, I see no reason to stay at 3.1.0 for my project. If problems appear that seem related, it's easy enough to drop back to 3.1.0 and see if that resolves them.
As for the suggestion that "One has to look at testing and experience with the combo", I know of no more likely thorough or reliable source for that experience than the UI project itself, so I'll defer to them.
Thanks again to all for their input, and apologies for the thrash.
Leave a comment on sparkpool's reply
I am running JQuery 3.4.1 and JQuery UI 1.12.1 and I also see this error:
JQMIGRATE: jQuery.expr.filters is deprecated; use jQuery.expr.pseudos
I found that in the _findPos function, there is still $.expr.filters which cause the warning:
while ( obj && ( obj.type === "hidden" || obj.nodeType !== 1 || $.expr.filters.hidden( obj ) ) ) {
Are you planning to provide a newer JQuery UI version that fix this issue?
Don’t expect a new version of UI any time soon.
Don’t use JQMIGRATE. It’s best used while upgrading. Once you have fixed the problems, you should remove it and go into final testing.
JΛ̊KE
Leave a comment on Ricky11's reply
Jake,
It's jQuery guidance to resolve all jqMigrate warnings. Removing jqMigrate would remove compatibility polyfills and potentially break your app.
These errors are bubbling up from jQueryUI as the original post suggested. A new jQueryUI has to be on the horizon otherwise it won't be compatible with current mainline jQuery.
Am I missing something?
/rafael
The latest version of jQuery UI is supposed to work with all versions of jquery from 1.7 to the current. If you find something that does not work, report it to the jquery UI bug site.
If you want to leave migrate on your site, It may work. But you will get warnings.Migrate is meant for you to see the warnings, fix them or otherwise upgrade. Then remove it.
The number of people actively working on UI is very low these days. You may see a bug fix release, but probably not a new version.
JΛ̊KE
Leave a comment on Rafael Rivera's reply
jQuery Migrate warnings are not just warnings we can ignore. jQuery Migrate often has a polyfill to fill in the gap; removal of jQuery Migrate could render the site unusable due to jQuery UI bugs.
This particular warning has been in jQuery Migrate for 2 years and we haven't seen a jQuery UI bugfix release to mitigate it. It sounds like we're on our own.
It's not clear if jQuery current + jQuery UI current are compatible without jQuery Migrate. And it's not clear if jQuery UI will ever release a fix.
I'll look into filing a bug, but looking at the tracker, it seems dead.
If you don't care to fix your own site to not rely on migrate, you will have warnings. UI does not require migrate.
JΛ̊KE
PS
Use migrate or don't. I don't care. And from the bug tracker, nobody seems to care.
Leave a comment on Rafael Rivera's reply
Jake, let me be very clear: These jQuery Migrate warnings are generated from jQuery UI code, not our code.
Sounds like you're suggesting developers ignore them, remove jQuery Migrate, and hope the deprecated APIs are removed before the next jQuery release.
That's terrible advice.
EDIT: Looks like this was fixed 2 years ago https://bugs.jqueryui.com/ticket/15185 / https://bugs.jqueryui.com/ticket/15196 and now we're just waiting for a jQuery UI release.
And the migrate warnings come from the migrate plugin, not UI. That's part of the job of migrate.
JΛ̊KE
Leave a comment on Rafael Rivera's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic
Reply to Андрей's problem
{"z694678020":[14737000008120065,14737000008120069,14737000008120071],"z2953239":[14737000007146558,14737000007146562,14737000007152361,14737000007164225],"z2656090":[14737000007146564,14737000007162061,14737000007162087],"z7664639":[14737000007162067,14737000007162089],"z690913480":[14737000008091229],"z7819078":[14737000007132020],"z2950240":[14737000007127089,14737000007150922,14737000007150932,14737000008089414,14737000008122029,14737000008122031,14737000008122033,14737000008122035]}