element.find() is not quite equivalent to element.querySelectorAll() about youmightnotneedjquery

[The4thLaw]

You need to use :scope, as described on this Mozdev article: https://developer.mozilla.org/en-US/docs/Web/API/Element/querySelectorAll

No support for IE, though.

[zackbloom]

I may not be understanding what you're referring to, but you can call querySelectorAll on any DOM node to get matches inside it:

someElement.querySelectorAll('.cats');

[agamemnus]

I know! Check out the jsfiddle...

Edit: my bad.. forgot to include jquery link in the fiddle.

[timmfin]

For anyone else that stumbles into this, here is a decent summary (visit some of the links/fiddles too) of the pros/cons of jquery vs querySelectorAll.

The biggest issue that sticks out to me (assuming it hasn't been elsewhere addressed in the past 5+ years) is how someElement.querySelectorAll('.element-outside-someElement .cats'); returns different results than jQuery(someElement).find('.element-outside-someElement .cats');

[varemenos]

DOMElement.querySelectorAll doesn't behave like $Element.find.

Here are some links discussing the issue:

http://ejohn.org/blog/thoughts-on-queryselectorall/
https://www.lvh.io/posts/queryselectorall-from-an-element-probably-doesnt-do-what-you-think-it-does.html