jQuery .find() vs context, using DOM node as context

JavaScript performance comparison

Revision 6 of this test case created


To modify the actual context of a selector (i.e. cause it to not search the default context - the entire document node - but instead scope to only the specified node) the context attribute must be a DOM Node - not a jQuery selector or even a jQuery collection. If a jQuery selector or collection is used, context acts simply as a wrapper for .find (and will therefore always be slower.)

src: http://brandonaaron.net/blog/2009/06/24/understanding-the-context-in-jquery

Preparation code

<script src="https://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js"></script>
<div id='myDiv'>
        <p>hello <a href="http://www.example.com/"><span class="mySpan">link</span></a></p>
        <p>world <a href="http://www.example.com/"><span class="mySpan">link</span></a></p>
  if (!window.console || !window.console.log) {
   throw 'console.log() is not supported. Please install Firebug. http://getfirebug.com'
Benchmark.prototype.setup = function() {
    var $myDiv = $("#myDiv"),
        myDiv = $myDiv[0];

Preparation code output

hello link

world link

Test runner

Warning! For accurate results, please disable Firebug before running the tests. (Why?)

Java applet disabled.

Testing in unknown unknown
Test Ops/sec
$('.mySpan', myDiv);

Compare results of other browsers


You can edit these tests or add even more tests to this page by appending /edit to the URL. Here’s a list of current revisions for this page:


Comment form temporarily disabled.

Add a comment