jQuery 1.0.3

21 thoughts on “jQuery 1.0.3”

1. huncent on October 28, 2006 at 12:50 am said:

   Thanks John,the docs is very helpful to me!
2. Jake on October 28, 2006 at 1:31 am said:

   Where’s the svn? —
   svn co svn://jquery.com/jquery

   subversion/libsvn_client/checkout.c:90: (apr_err=170000)
   svn: URL ‘svn://jquery.com/jquery’ doesn’t exist
3. John Resig on October 28, 2006 at 2:19 am said:

   SVN just went through a little bit of a re-org, you can now get it here: svn://jquery.com/trunk/jquery Sorry for the confusion.

4. Pingback: Nueva version jQuery 1.0.3 - aNieto2K

5. Andrey Skvortsov on October 28, 2006 at 5:48 am said:

   So,what about:
   http://jquery.com/blog/2006/10/13/minor-api-change-in-102/#comment-3582
   Thanks.
6. Steve O on October 28, 2006 at 10:05 am said:

   When I try to use 1.0.3, I get a javascript error because of the following line:

   1015: event.target = event.srcElement;

   The error I get (only in IE, which is consistent with the above since line 1015 is in the if (jQuery.browser.msie) block). The above line is not in 1.0.2, which works just fine for me.

   The error IE complains about is:
   ‘null’ is null or not an object
7. John Resig on October 28, 2006 at 11:35 am said:

   @Andrey: The best way to get the raw XMLHttpRequest object is to have a ‘complete’ handler, for example:

   $.ajax({
     url: "test.html",
     complete: function(res){
       // res == The XMLHttpRequest Object
     }
   });

   @Steve: Are you able to duplicate it consistently? Could you post a bug to the bug tracker with Critical priority, if that’s the case?
8. pac on October 28, 2006 at 5:03 pm said:

   @Steve / @John: Get the same error in IE when i make an $.ajax() call…

   I posted a this as critical in bug tracker.

9. Pingback: sorgalla.com - jCarousel now with jQuery 1.0.3

10. Andrey Skvortsov on October 29, 2006 at 6:50 am said:

    Thanks for suggestion,John,so you say XmlHTTPRequest available only for generic ajax requests? $.get,post,load are out of luck?It’s not very consistent for framework,don’t you think?And if you accept that I say,why put such constraints in the first place?

    Best wishes.
11. Andrey Skvortsov on October 29, 2006 at 7:19 am said:

    By the way,why $.ajax has success/complete/… separation but other ajax functions dosen’t?So,I have to use function(xml,status){} signature all the time and check for “success” myself using “status”.Could you,please,provide more consistent programming model for ajax requests?

    Thanks.
12. Essen on October 29, 2006 at 1:56 pm said:

    Wouldn’t it be better to you write the test to “prevent execution of jQuery if included more then once” (the one at the beginning) outside the eval block in the compressed file?

    I’m not really sure but I think it would prevent the parsing of the eval block and thus be faster.
13. Rob on October 30, 2006 at 9:19 am said:

    Not sure if this is a bug or something intentional but with 1.0.3 when animating objects they now seem to quickly fade-in and fade-out.

    Thank you so much for all your incredible work!
14. Roy Kolak on October 30, 2006 at 3:52 pm said:

    great work guys
15. Jason on October 31, 2006 at 4:49 am said:

    It looks like a lot of bug fixes, but unfortunately I can’t upgrade. Whatever has changed has caused the tabs plugin to not work correctly in IE. I’d submit a bug report, but I have no idea on what the problem might be.
16. Jason on October 31, 2006 at 4:49 am said:

    It could just be a problem with the plugin itself, of course. :)
17. Andrey Skvortsov on October 31, 2006 at 6:58 am said:

    Small bug(feature)-if you’are using saveHistory behavior(very useful feature for “form” element) of IE-getAttribute/setAttribute methods are “blocked/overrided”,hence $().attr() dosen’t work at all.You have been warned;-)

    Best wishes.
18. Ardie on October 31, 2006 at 9:39 pm said:

    Found a bug with using hover event binding in IE. Memory keeps spiking whenever i hover over any elements that went through the hover binding process. Also noticed that the IE memory leak hasn’t been addressed yet. (Memory leak whenever the page refreshes)

    function navMenu()
    {
    if ($.browser.msie)
    { /* memory leak */
    $(“#navMain”).find(“#navMain > li”).hover(function()
    {
    $(this).addClass(hoverCss);
    },
    function()
    {
    $(this).removeClass(hoverCss);
    });
    }
    }
19. Jörn on November 1, 2006 at 5:45 am said:

    @Essen:

    If you have enough control over your page to worry about performance, you can just avoid including jQuery more then once, therefore preventing any performance issues. The check is necessary for cases where you don’t have that control.

    @all bug reporters:

    Could you please use the bug reporting (http://jquery.com/dev/bugs/new/) to post bugs? Thats helps a lot to keep thing organized and getting them done. Thanks!
20. reprogramacion on November 5, 2006 at 8:40 pm said:

    AOL Active Virus Shield recognizes jQuery like a virus: Trojan program Trojan-Downloader.JS.Psyme.cm
21. Fotis Evangelou on December 5, 2006 at 12:38 pm said:

    Hello John, everyone!

    I wanted to let you know that it seems Jquery is having a conflict with the latest Mootools library. I am not a .js script kiddie at all, but I noticed that if mootools is activated AFTER JQuery, then it cuases issues with scripts written in JQuery. I am a Joomla developer and have created 2 extensions in my demo site at http://demo.joomlaworks.gr, the one uses JQuery (the Header Rotator) and the other (Simple Image Gallery) uses Mootools.

    Changing the order of the scripts solves the problem. I tried various activations/deactivations with both libraries and it seems that the problem is only with JQuery.

    Thanks in advance for any input/feedback on this.

    Fotis Evangelou
    JoomlaWorks.gr