8 ms·

JQuery 1.9 has been released

202 points by jonknee 14y ago

ecaron 14y ago
For anyone making a shift from 1.7/1.8 to this, please don't overlook the jquery-migrate plugin (https://github.com/jquery/jquery-migrate/ https://github.com/jquery/jquery-migrate/). You/we don't have to suffer the headaches of "what the heck changed since the version I was using...", the jQuery overlords have really done us a great service in offering this cool migration checker - so let's use it!
- zalew 14y ago
  that's what I got when using jquery migrate http://i.imgur.com/nviTD.png http://i.imgur.com/nviTD.png not that helpful, or am I missing something?
  - mattparlane 14y ago
    Those are warnings to let you know that you are using deprecated functionality. Everything should still work, but you'll want to switch to the updated versions soon. Instead of $.browser, use $.support, and instead of .live(), use .on().
    - zalew 14y ago
      I get it, but I thought it would map the occurences in my code, not just list the functions.
      - mattparlane 14y ago
        Ah, gotcha. If you have the console open at the time when the warning is triggered, you should be able to get a backtrace by clicking on the arrow beside the warning -- that will show you whereabouts in the code the problem is. At least that's how it works in Chrome, I think Firefox does the same.
        zalew 14y ago
        no arrow in ff (firebug 1.11.1) nor in chromium (firebug lite).
        joshschreuder 14y ago
        zalew, try out the Chrome dev tools (hit CTRL-SHIFT-I)
  - dmethvin 14y ago
    * Click on the hyperlink for the line where the message was generated. * Set a breakpoint. * Refresh the page. * View the stack trace(s). Adding stack traces to the plugin itself would be difficult, since that's not standardized functionality and it would add quite a bit of bulk to the plugin.
- didip 14y ago
  So, how does one use jquery-migrate? Include the script tag and... Will it show me which method (in which file) to replace in console?
  - morphir 14y ago
    https://github.com/jquery/jquery-migrate/#readme https://github.com/jquery/jquery-migrate/#readme
techtalsky 14y ago
Nothing too terribly exciting, but the Source Map feature, allowing easier debugging inside minified code seems very useful. Chrome only, but still an extremely slick feature: http://www.html5rocks.com/en/tutorials/developertools/sourcemaps/ http://www.html5rocks.com/en/tutorials/developertools/source...
- scott_karana 14y ago
  > Chrome only, but still an extremely slick feature Only for now, fortunately! The co-authors are from Google and Mozilla[1], and work's being done to get support in Firefox as well. [1] https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k/edit?hl=en_US&pli=1&pli=1 https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiO...
- novaleaf 14y ago
  iirc, visual studio supports source map debuging too. (at least it does for typescript generated code)
mildweed 14y ago
Important for those who haven't heard yet: jQuery 2.0 will not support IE 6, 7 or 8.
- agildehaus 14y ago
  I can understand dropping 6 and 7, but 8? That browser's not going away anytime soon.
  - fernandezpablo 14y ago
    It's going to have support for al IEs but as an official plugin and not in the main distribution (which is a good thing IMHO)
    - blowski 14y ago
      Do you have a link for that? I've only seen them say "if you need to support IE8, you need to use jQuery 1.9". No mention of a plugin.
  - jneal 14y ago
    They are continuing support for both 1.9 (supporting IE6+) and 2.0
  - huxley 14y ago
    As I understand it, JQuery 1.9 and 2.0 are supposed to be API identical so what is suggested is to offer JQuery 1.9 to sub-IE9 via conditional comments.
    - indeyets 14y ago
      That's one of the ways, but you can just stick to 1.9 for all of your audience if audience includes early IEs. jQuery 2.0 is more appropriate for mobile web-apps or for intranets, where you know that users use strict subset of browsers
      - 14y ago
jneal 14y ago
I'm happy for the addition of the :target selector. I tried using this on a recent project before realizing it wasn't available.
TallboyOne 14y ago
How has everyone's experience so far been upgrading? Any speed improvements?
- daGrevis 14y ago
  In theory, jQuery 2 should be a lot faster because of removed support for old browsers.
deleted 14y ago
[deleted]
haydenchambers 14y ago
Is the size reduction in 2.0 really only 16kb? 1.9 252kb uncompressed 2.0 236kb uncompressed
joell 14y ago
Be careful if you are using this link as a source: https://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js https://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js A few things in this update broke a production app for us.

202 points by jonknee 14y ago

For anyone making a shift from 1.7/1.8 to this, please don't overlook the jquery-migrate plugin (https://github.com/jquery/jquery-migrate/ https://github.com/jquery/jquery-migrate/). You/we don't have to suffer the headaches of "what the heck changed since the version I was using...", the jQuery overlords have really done us a great service in offering this cool migration checker - so let's use it!

zalew 14y ago
that's what I got when using jquery migrate http://i.imgur.com/nviTD.png http://i.imgur.com/nviTD.png not that helpful, or am I missing something?
- mattparlane 14y ago
  Those are warnings to let you know that you are using deprecated functionality. Everything should still work, but you'll want to switch to the updated versions soon. Instead of $.browser, use $.support, and instead of .live(), use .on().
  - zalew 14y ago
    I get it, but I thought it would map the occurences in my code, not just list the functions.
    - mattparlane 14y ago
      Ah, gotcha. If you have the console open at the time when the warning is triggered, you should be able to get a backtrace by clicking on the arrow beside the warning -- that will show you whereabouts in the code the problem is. At least that's how it works in Chrome, I think Firefox does the same.
      - zalew 14y ago
        no arrow in ff (firebug 1.11.1) nor in chromium (firebug lite).
      - joshschreuder 14y ago
        zalew, try out the Chrome dev tools (hit CTRL-SHIFT-I)
- dmethvin 14y ago
  * Click on the hyperlink for the line where the message was generated. * Set a breakpoint. * Refresh the page. * View the stack trace(s). Adding stack traces to the plugin itself would be difficult, since that's not standardized functionality and it would add quite a bit of bulk to the plugin.
didip 14y ago
So, how does one use jquery-migrate? Include the script tag and... Will it show me which method (in which file) to replace in console?
- morphir 14y ago
  https://github.com/jquery/jquery-migrate/#readme https://github.com/jquery/jquery-migrate/#readme

techtalsky 14y ago

Nothing too terribly exciting, but the Source Map feature, allowing easier debugging inside minified code seems very useful. Chrome only, but still an extremely slick feature: http://www.html5rocks.com/en/tutorials/developertools/sourcemaps/ http://www.html5rocks.com/en/tutorials/developertools/source...

scott_karana 14y ago
> Chrome only, but still an extremely slick feature Only for now, fortunately! The co-authors are from Google and Mozilla[1], and work's being done to get support in Firefox as well. [1] https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k/edit?hl=en_US&pli=1&pli=1 https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiO...
novaleaf 14y ago
iirc, visual studio supports source map debuging too. (at least it does for typescript generated code)

mildweed 14y ago

Important for those who haven't heard yet: jQuery 2.0 will not support IE 6, 7 or 8.

agildehaus 14y ago
I can understand dropping 6 and 7, but 8? That browser's not going away anytime soon.
- fernandezpablo 14y ago
  It's going to have support for al IEs but as an official plugin and not in the main distribution (which is a good thing IMHO)
  - blowski 14y ago
    Do you have a link for that? I've only seen them say "if you need to support IE8, you need to use jQuery 1.9". No mention of a plugin.
- jneal 14y ago
  They are continuing support for both 1.9 (supporting IE6+) and 2.0
- huxley 14y ago
  As I understand it, JQuery 1.9 and 2.0 are supposed to be API identical so what is suggested is to offer JQuery 1.9 to sub-IE9 via conditional comments.
  - indeyets 14y ago
    That's one of the ways, but you can just stick to 1.9 for all of your audience if audience includes early IEs. jQuery 2.0 is more appropriate for mobile web-apps or for intranets, where you know that users use strict subset of browsers
    - 14y ago

jneal 14y ago

I'm happy for the addition of the :target selector. I tried using this on a recent project before realizing it wasn't available.

TallboyOne 14y ago

How has everyone's experience so far been upgrading? Any speed improvements?

daGrevis 14y ago
In theory, jQuery 2 should be a lot faster because of removed support for old browsers.

deleted 14y ago

[deleted]

haydenchambers 14y ago

Is the size reduction in 2.0 really only 16kb? 1.9 252kb uncompressed 2.0 236kb uncompressed

joell 14y ago

Be careful if you are using this link as a source: https://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js https://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js A few things in this update broke a production app for us.