-
Notifications
You must be signed in to change notification settings - Fork 20.6k
Remove context and selector properties #1908
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
Comments
Both of them are still in the code only because Migrate needs them to restore @dmethvin, what do you think? |
I haven't thought about it lately, but when I was doing this earlier I couldn't figure out a simple way to expose it for Migrate. We could move it to another property like |
I'd rather have Migrate duckpunch |
Hmmm, since we already mess with |
How can we get the original selector string that was used to invoke a plugin from within the plugin? Example:
I would like |
A closed ticket isn't the right place to look for support, but in general there is no string that represents the collection a plugin receives, e.g. |
Originally reported for jQuery 2.0.3 by anonymous at http://bugs.jquery.com/ticket/14341
Both properties have been deprecated since 1.10/2.0, the former courtesy http://bugs.jquery.com/ticket/13801
3.0 strikes me as the right time. Pre-1.10 #1249 probably can't be applied directly anymore, but I'll bet it's pretty close.
The text was updated successfully, but these errors were encountered: