Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Handle child selectors in particular - away from the selector engine.…
… Fixes #7029.
- Loading branch information
Showing
2 changed files
with
9 additions
and
1 deletion.
There are no files selected for viewing
This file contains 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
This file contains 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
f1f6bc3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the reason for the switch ?
f1f6bc3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're deprecating the >-prefixed style of selectors (removing it from Sizzle).
f1f6bc3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That stinks. Not part of querySelectorAll, but damned useful.
f1f6bc3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thus leaving
yes??EDIT: nvm...durrr
f1f6bc3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jupiterjs: Not sure what what the problem is - we're still supporting the > prefix in .find() - which is used everywhere in jQuery - but the > prefix isn't part of selector engines and we need to stop using it. Note that we've been doing similar for other parts of the selector engine as well (e.g. :last -> .last(), :eq -> .eq(), etc.)