jQuery 1.1.4: Faster, More Tests, Ready for 1.2

71 thoughts on “jQuery 1.1.4: Faster, More Tests, Ready for 1.2”

1. Martin on August 24, 2007 at 4:29 am said:

   Jquery 1.4 and IE6 seem to have Problems.
2. mbyte on August 24, 2007 at 4:34 am said:

   Great work!
   It work’s on Safari 3 win!
   I like it.

   Thank you!
3. Sharon Rosner on August 24, 2007 at 5:26 am said:

   There’s a mistake in the deprecations section:

   $.ajaxSettings({timeout: 3000});

   should be:

   $.ajaxSetup({timeout: 3000});
4. Tzury bar Yochay on August 24, 2007 at 5:30 am said:

   What about IE7? Is JQuery compatible with that one?
5. Robin on August 24, 2007 at 5:31 am said:

   Yes, IE7 works fine.
6. zinosoufi on August 24, 2007 at 5:44 am said:

   What explains this impressive performance improvement ?
7. Anders on August 24, 2007 at 5:47 am said:

   Wonderful! Great! Looking forward to the upcoming 1.2 release!

   By the way, the link to the jQuery test suite doesn’t work.

   /Anders
8. Michael on August 24, 2007 at 7:13 am said:

   Awesome! Can’t wait till jQuery 1.2 & jQuery UI

   What about Safari 2 though…?
9. SeViR on August 24, 2007 at 7:37 am said:

   I can not find slide() method in jQuery 1.1.4 . I see the code, download the svn trunk branch, but any slide() method is found.
   ???

   jQuery 1.1.4 works with all my current projects based in 1.1.2 and more fast, perfect!! :-D
10. Danny on August 24, 2007 at 8:25 am said:

    Is this a typo: $(“a[href]”) ? The documentation says that css attribute selectors should have @. I tried without it $(input[type=’text’]) and it didn’t work.
11. Dan G. Switzer, II on August 24, 2007 at 10:06 am said:

    @Martin:

    You say that v1.1.4 and IE6 have problems. What are the problems you’re experiencing?
12. John Resig on August 24, 2007 at 10:14 am said:

    @Shanon: Good catch, I’ll fix that in the post.

    @Danny: That’s correct. a[href] is the correct CSS syntax for selecting anchors with an attribute of href. You’ll also note that this change isn’t being made until jQuery 1.2 AND that you’ll still be able to use the @, if you’d like. There’s no need to worry about it now.

    @Everyone: Yes, we also test in Safari 2 and IE 7, they just weren’t mentioned for brevity.
13. Wade Harrell on August 24, 2007 at 12:20 pm said:

    // Put jQuery in a namespace:
    var obj = {};
    obj.jq = jQuery.noConflict(true);
    obj.jq(“#id div”).hide();

    looks very interesting but will this play nicely with plugins? com.jQ would work very nice with the namespaces I use in my apps. I am just concerned that plugins may act up if not assigned beforehand. Guess I will find out soon enough ;)
14. hadi farnoud on August 24, 2007 at 12:31 pm said:

    OMG, Safari 3 is fastest browser i ever seen! Apple ROCKS
15. Aaron on August 24, 2007 at 12:38 pm said:

    That’s funny, just tried the tests in Firefox 2.0.0.6, and 10 tests failed.

    selector module: id (2, 5, 7)
    # Died on test #6: TypeError: a[i] has no properties
    # Expected 24 assertions, but 6 were run

    selector module: class (6, 10, 16)
    # Class selector using UTF8 (.台北Táiběi) expected: [ span#utf8class1 ] result: [ ]
    # Class selector using UTF8 (.台北) expected: [ span#utf8class1, span#utf8class2 ] result: [ ]
    # Class selector using UTF8 (.台北Táiběi.台北) expected: [ span#utf8class1 ] result: [ ]
    # Class selector using UTF8 (.台北Táiběi, .台北) expected: [ span#utf8class1, span#utf8class2 ] result: [ ]
    # Descendant class selector using UTF8 (div .台北Táiběi) expected: [ span#utf8class1 ] result: [ ]
    # Child class selector using UTF8 (form > .台北Táiběi) expected: [ span#utf8class1 ] result: [ ]

    selector module: attributes (2, 9, 11)
    # Died on test #10: TypeError: a[i] has no properties
    # Expected 20 assertions, but 10 were run

    It seems like I get these errors in every browser I test it in.

    … That said, I moved one of my projects over to the new version, and things are working flawlessly. So, bravo, but a slightly hesitant bravo.
16. Charles on August 24, 2007 at 1:26 pm said:

    Fantastic selector speedup, good to see features being condensed and deprecated. Very excited about slice()! I am interested to see some speed tests on that function.

    Unfortunately I get the same results as Aaron when I run the test suite in FF 2.0.0.6.

    I will let y’all know how the upgrade goes!
17. Andrew Chalkley on August 24, 2007 at 1:30 pm said:

    Well done again for the speed increases.

    There are some truly amazing projects and each getting optimized more and more.

    For example the HAML interpretor has recently increased it’s rendering engine and looking to get faster than erb.
18. Adam Skinner on August 24, 2007 at 1:42 pm said:

    So people who are currently using $(‘div[p]’) should now use $(‘div:has(p)’), but people who are using $(‘div[@p]’) should now use $(‘div[p]’)?!

    If they don’t change the $(‘div[p]’), this will change the functionality to the old @ functionality instead of the has: functionality, right?

    Also, just as an aside, I was using jQuery in a Chickenfoot script, and while 1.1.3.1 works, 1.4 doesn’t (it can’t even find $ or jQuery).
19. Brett on August 24, 2007 at 2:04 pm said:

    I ran the test suite and had 10 failures.

    Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6

    Tests completed in 53041 milliseconds.
    10 tests of 790 failed.

    Here are the details: (the items with – in front of them failed.)

    62. selector module: id (2, 5, 7)
    1. ID Selector (#body)
    2. ID Selector w/ Element (body#body)
    3. ID Selector w/ Element (ul#first)
    4. ID selector with existing ID descendant (#firstp #simon1)
    5. ID selector with non-existant descendant (#firstp #foobar)
    – 6. Died on test #6: TypeError: a[i] has no properties
    – 7. Expected 24 assertions, but 6 were run

    63. selector module: class (6, 10, 16)
    1. Class Selector (.blog)
    2. Class Selector (.blog.link)
    3. Class Selector w/ Element (a.blog)
    4. Parent Class Selector (p .blog)
    – 5. Class selector using UTF8 (.台北TáibeÌŒi) expected: [ span#utf8class1 ] result: [ ]
    – 6. Class selector using UTF8 (.台北) expected: [ span#utf8class1, span#utf8class2 ] result: [ ]
    – 7. Class selector using UTF8 (.台北TáibeÌŒi.台北) expected: [ span#utf8class1 ] result: [ ]
    – 8. Class selector using UTF8 (.台北TáibeÌŒi, .台北) expected: [ span#utf8class1, span#utf8class2 ] result: [ ]
    – 9. Descendant class selector using UTF8 (div .台北TáibeÌŒi) expected: [ span#utf8class1 ] result: [ ]
    – 10. Child class selector using UTF8 (form > .台北TáibeÌŒi) expected: [ span#utf8class1 ] result: [ ]
    11. Escaped Class (.foo\:bar)
    12. Escaped Class (.test\.foo\[5\]bar)
    13. Descendant scaped Class (div .foo\:bar)
    14. Descendant scaped Class (div .test\.foo\[5\]bar)
    15. Child escaped Class (form > .foo\:bar)
    16. Child escaped Class (form > .test\.foo\[5\]bar)

    66. selector module: attributes (2, 9, 11)
    1. Attribute Exists (a[@title])
    2. Attribute Exists (*[@title])
    3. Attribute Exists ([@title])
    4. Attribute Equals (a[@rel=’bookmark’])
    5. Attribute Equals (a[@rel=”bookmark”])
    6. Attribute Equals (a[@rel=bookmark])
    7. Multiple Attribute Equals (input[@type=’hidden’],input[@type=’radio’])
    8. Multiple Attribute Equals (input[@type=”hidden”],input[@type=’radio’])
    9. Multiple Attribute Equals (input[@type=hidden],input[@type=radio])
    – 10. Died on test #10: TypeError: a[i] has no properties
    – 11. Expected 20 assertions, but 10 were run
20. AjaxDev0008 on August 24, 2007 at 2:07 pm said:

    $(…).evalScripts() Still seems to be required for IE when using something like:
    $.ajax({
    type: “POST”,
    dataType: “html”,
    url: “testAjax.jsp”,
    data: “name=John&location=Boston”,
    success: function(msg){
    $(“div.changeThis”).append(msg);

    }
    });
    Am I missing something?
21. John Resig on August 24, 2007 at 2:08 pm said:

    @Aaron and Charles: I’ve fixed the suite – it wasn’t checked out properly. Go here instead: http://jquery.com/test/

    @Adam: No one should make the switch away from [@foo] -> [foo], because it simply won’t be possible until jQuery 1.2 (because of the obvious API incompatibility). And even so, in 1.2, [@foo] will only be deprecated – it’ll still work (too many plugins and code bases rely on having it still work that way).

    Also, in relation to the Chickfoot item, it might be because we now do window.jQuery now instead of ‘var jQuery’ – hmm, I wonder how we might work around that.
22. John Resig on August 24, 2007 at 2:12 pm said:

    @Brett: I checked out the wrong copy of the suite, please try this new one:
    http://jquery.com/test/

    @AjaxDev0008: Nope – evalScripts is no longer required here! Isn’t it nice?
23. Charles on August 24, 2007 at 2:17 pm said:

    @John:

    Passed with flying colors! I love the attitude around here… “When a problem comes along, you must whip it.”
24. AjaxDev0008 on August 24, 2007 at 2:24 pm said:

    @John Resig: Tested without using evalScripts in IE 6 and 7. Used a simple alert in the file that was called by $.ajax.
    I am afraid the alert was not called when the msg was appended.

    Anyone else test this yet?

    Works in Firefox though.
25. John Resig on August 24, 2007 at 2:30 pm said:

    @AjaxDev0008: We have tests for this in our suite – and it is passing in IE 6. Do you have a demo page that I can see? Maybe I can spot the problem.
26. Blair Mitchelmore on August 24, 2007 at 2:32 pm said:

    @Wade

    I’m not sure how it’s been implemented as I haven’t looked into the code yet, but my guess would be that plugins will play nice as long as they are defined before .noConflict is called. After that they’re probably out of luck.
27. Adam Skinner on August 24, 2007 at 3:14 pm said:

    @John Resig: you are, of course, the man.

    
include('http://jqueryjs.googlecode.com/files/jquery-1.1.4.pack.js');
$ = window.jQuery;
output($);


    works.

    Is window.jQuery (effectively) mutually exclusive with var jQuery? I mean, are you doing that so we can do the “Any Name jQuery”?
28. John Resig on August 24, 2007 at 3:30 pm said:

    @Adam: Correct, that is part of the “any name” stuff. I’m not sure how ChickenFoot works, in particular – but this may just be a caveat that’ll need to be taken into consideration, in order to use it.
29. AjaxDev0008 on August 24, 2007 at 4:34 pm said:

    @John Resig: I don’t have a demo page available but here is the code that I am using:

    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"&gt;
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
    <title> test </title>

    <script type="text/javascript" src="javascripts/jquery.js"></script>
    <script type="text/javascript">

    function clickMe(){
    $.ajax({
    type: "POST",
    url: "ajaxTest.htm",
    dataType: "html",
    success: function(msg){
    $(‘div#test’).append(msg);
    }
    });
    }

    </script>
    </head>
    <body>
    <div>
    <input type="button" value="Click Me" onclick="clickMe();"/>
    </div>
    <div id="test">Some Text</div>
    </body>
    </html>

    And here is the content of ajaxTest.htm:

    <div>
    Some more text
    <script type="text/javascript">
    alert(‘Hello’);
    </script>
    </div>
30. Paul on August 24, 2007 at 4:52 pm said:

    Hi,

    I have some problems with $.ajax. My code worked very well with the 1.1.3.1 but does not work anymore with 1.1.4.1.

    Here is the code (all variables are defined previously and work correctly with the previous version in IE7).

    $.ajax({
    url: sUrl,
    data: sParams, // detected parameters
    type: sMethod,
    dataType: ‘html’,
    timeout: 30000,
    error: function(object,message){
    $(sMessageId).html(“Erreur de chargement! “+message+””);
    },
    success: function(html){
    $(sTarget).html(html); // detected target
    $(“#message”).html(“”);
    },
    beforeSend: function(){
    $(sMessageId).html(“”);
    }
    });

    The beforeSend event is triggered but the error, or succes events aren’t. Thit I miss something?

    ;)

    Paul
31. Renato Carvalho on August 24, 2007 at 5:24 pm said:

    Wow! Great improvements.

    Thanks!
32. Nilesh on August 24, 2007 at 10:37 pm said:

    Glad to see creative updates into jquery, and plugin pages updates very nicely every few days, will be good jump to 1.2, woo!,

    thank much to the very active community! and resource, well organized , good documents and examples.

    cheers to all,
    Nilesh P.
33. ziggy on August 24, 2007 at 11:23 pm said:

    I want to get all the recent speed increases but since 1.1.3 came along my photoviewer is doing weird things because of something that changed in jquery relating to animations, I believe. 1.1.4 has the same problems.

    a) Firefox: I have a row of 6 thumbnails but when the containing viewer is closed now (toggle(‘slow’)), the row breaks after the 5th thumbnail and the last thumbnail drops onto a new second line just before the viewer closes. Somehow it appears to be increasing margins or something when display is toggled so the row no longer fits.

    b) In IE7 it doesn’t do that but instead closes in a slow, odd, step-like manner: click close, pause, then the opacity effect on the background disappears so background goes black, another pause, then closes.

    Ideas on how to overcome these issues?

    Thanks.
34. qui est regex? on August 24, 2007 at 11:36 pm said:

    And still no regex selectors. Unbeleivable.
35. John Resig on August 25, 2007 at 12:06 am said:

    @qui est regex: You do realize that we don’t add functionality in minor releases, right? we only add new stuff in major releases? The methods that we added this time we necessary in order to transition people away from the deprecated methods – there’s no such case with regexp selectors.
36. Ralph Whitbeck on August 25, 2007 at 7:37 am said:

    Holy Snikeys!

    The speed improvements to the ID selector alone is just awe inspiring.

    Great work John and team!
37. Johann on August 25, 2007 at 7:56 am said:

    So far, no problems with my plugins. Thanks!
38. Rick on August 25, 2007 at 9:10 am said:

    Hey this may be a bit off-topic, but I just watched your entire presentation of Javascript Libraries of about a week ago, John. It’s pretty impressive and I learned a lot from it, about Javascript but also about jQuery. Awesome release by the way.
39. MikeChristensen on August 25, 2007 at 11:14 am said:

    John,

    I was reading your jQuery 1.2 Roadmap and noticed that you mentioned the possibility of including livequery into jquery if you saw a more widescale adoption of its use. Well, I’m here to testify that it is a main file included on every page of the enterprise-level site we’re building.

    I was starting to get sick of writing initialize $.fn’s and livequery saved the day. After using the selector to bind an event to what is matched, there are many instances in which we Ajax in new content that needs the same event applied after DOM has loaded. Without livequery, we have to reassign events to the Ajaxed content. Of course my only concern is the eventual need for garbage collection on event triggers never used during the page view, but I’m sure some genius will come up with a plan for that.

    If adding livequery to jQuery means I save a couple of bytes of overhead for file inclusion and overall filesize, I say “do it!”
40. MikeChristensen on August 25, 2007 at 11:19 am said:

    By the way. I can’t thank you enough for jQuery. It has opened the doors for many possibilities and lent me the ability to create feature-rich applications I couldn’t have done with simply reading DOM javascript books.

    Thanks again.
41. Max on August 26, 2007 at 10:48 am said:

    Great, thanks!
42. Denis Ignatenko on August 27, 2007 at 12:41 am said:

    @MikeChristensen
    >>Well , I’m here to testify that it is a main file included on every page of the enterprise-level site we’re building.
    If you need some plugins with core lib, so why not to build jQuery and livequery together in a single file? As for me I see no reason for merging.
43. frankysanders on August 27, 2007 at 2:16 am said:

    I too seem to be having issues with IE 6.0 and evalScripts.

    I had to write a little hack.

    $(“#” + id + “”).html(result);
    if(getBrowser == “msie”){
    $(“#” + id + “”).evalScripts();
    }

    I’ve tested this as follows:
    1) create an ajax chunk

    function test(){
    alert(1);
    }
    test();

    Try to load this via the .ajax method and the alert will not be executed in IE 6. I am not currently able to test this in IE 7 but I suspect similar behavior.
44. frankysanders on August 27, 2007 at 5:15 am said:

    I’ve moved some code around and all seems to be good now. I am not sure what fixed it but this bug no longer is affecting my application.
45. Don on August 27, 2007 at 8:26 am said:

    How about a new slickspeed addin for 1.1.4 ??
46. AjaxDev0008 on August 27, 2007 at 8:54 am said:

    @frankysanders
    Can you post the changes you made to your code to make the .Ajax bug go away?
47. Jim on August 27, 2007 at 10:01 am said:

    http://jquery.com/test/ crashes my Safari Version 2.0.4 (419.3) Mac
    Successfully crashed it thrice.
48. Jim on August 27, 2007 at 10:05 am said:

    I should mention… jQuery is awesome.
49. Ariel Flesler on August 27, 2007 at 12:21 pm said:

    @MikeChristensen:
    The re-binding problem you mention, can be easily avoided using event delegation, jquerylive is a great plugin but you can just bind functions to the containers, that don’t get refreshed with ajax calls and that will work just fine.
    I posted a small plugin for event delegation, it’s called Intercept. It’s pretty simple right now, maybe it helps you out.
50. Vlad on August 27, 2007 at 1:10 pm said:

    Respect for your hard job!
    Very nice and fast lib! ;-)