No ticket: remove selector and context properties #1249
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
These are publicly documented parts of the API http://api.jquery.com/context/ I can't find a/the ticket for removal (maybe there isn't one?) |
|
Well, at least Also, is it sth that's easy to add to jQuery Migrate? I thought that's the reason they still exist that it would be hard to cleanly add them as a plugin. |
|
OMFG. |
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As far as I can tell, the
contextproperty of jQuery collections exists only to let jquery-migrate monkey-patch.liveand.die, andselectoris completely unnecessary. We should move necessary code into that plugin and cut our undocumented ties with the past.