I actually would like to keep them all. [":"] is probably the most prevalent in user code and needs to stay regardless. filters has been there a long time, but it wasn't used as much. And pseudos is NWMatchers' name for filters, so it's a more intuitive name to some.

Regardless, I'd like to continue recommending the use of the .createPseudo() method for creating custom selectors, making the choice of one property somewhat moot – except for setFilter. jQuery UI already uses it where available.

I actually would like to keep them all.

In the sense of not moving to deprecated, or of not standardizing?

[":"] is probably the most prevalent in user code and needs to stay regardless.

But still exceedingly rare from (among other things) its lack of documentation, and with a fix that couldn't be simpler. At any rate, though, I propose deprecation not because I think we can remove them anytime soon, but to promote consistency.

filters has been there a long time, but it wasn't used as much.

That would depend on your measurement criteria... it's probably the most used by execution count from jQuery UI alone. And to the extent that any such special-case functionality can be used "much", I bet updating api.jquery.com would address the educational gap.

And pseudos is NWMatchers' name for filters, so it's a more intuitive name to some.

Then it appears NWMatcher has moved on, at least from an API perspective (which is what I'm addressing). However, even if it hadn't, maintaining surface area in jQuery core to support transitioning from an independent selector engine seems... overaccommodating.

Regardless, I'd like to continue recommending the use of the .createPseudo() method for creating custom selectors, making the choice of one property somewhat moot – except for setFilter.

Not at all; the result of createPseudo still has to be assigned to an object property. e.g.: data: $.expr.createPseudo…

That would depend on your measurement criteria... it's probably the most used by execution count from jQuery UI alone. And to the extent that any such special-case functionality can be used "much", I bet updating api.jquery.com would address the educational gap.

I think we're on different wavelengths here. In terms of defining custom pseudos, you said jQuery UI mostly used [":"] and only used .filters once. Still, I was referring to user code in general and I just remember seeing [":"] much more often. Maybe my memory is off.

Not at all; the result of createPseudo still has to be assigned to an object property. e.g.: data: $.expr.createPseudo…

Totally true. Brain fart. However, the main point there was createPseudo isn't in jQuery's documentation either.

I'm all for documenting custom pseudo creation in jQuery (and I'm fine picking a property and sticking with it), but I still don't see the value behind deprecating the other properties. To me, deprecation voices the intention of removal whether we say it does or not. If we use the same property in all of our documentation, that seems like enough.

Per meeting, decided on "pseudos".