We’re carefully watching Android 2.x market share to determine when we can cross it off the support list, and don’t expect it to take very long.Ĭustom builds for even smaller files: This feature has been greatly refined and extended since its debut in jQuery 1.8. We had hoped to remove even more code and increase performance, but older Android/WebKit 2.x browsers are now the weakest link.
Reduced size: The final 2.0.0 file is 12 percent smaller than the 1.9.1 file, thanks to the elimination of patches that were only needed for IE 6, 7, and 8. If you can use the HTTP header it is slightly better for performance because it avoids a potential browser parser restart. To prevent these newer IE versions from slipping back into prehistoric modes, we suggest you always use an X-UA-Compatible tag or HTTP header. No more support for IE 6/7/8: Remember that this can also affect IE9 and even IE10 if they are used in their “Compatibility View” modes that emulate older versions. Here are some highlights of the changes that jQuery 2.0 brings:
Even better, we’d love for the communities supporting these environments to pool and share their knowledge about how to use jQuery 2.0 there. Although we aren’t able to test regularly in all of these non-browser scenarios, we’d like to hear about your experiences in using jQuery with them. Many of these environments are themselves a work in progress, and have unique sets of rules or restrictions that are different from the ones typically found when jQuery is used for browsers on Internet web sites. node.js (combined with jsdom or similar).Windows 8 Store (“Modern/Metro UI”) apps.Mozilla XUL apps and Firefox extensions.These are typically non-web-site scenarios where support for older IE isn’t relevant. With the release of jQuery 2.0, there are a few environments where the jQuery team will no longer support use of the 1.x line because 2.x is a far better choice. The simplest way to support older browsers is to use jQuery 1.x on your site, since it works for all browsers. If you want, you can serve 2.0 to newer browsers and 1.9 to older ones using our conditional comment trick, but that is not required. JQuery 2.0 is intended for the modern web we’ve got jQuery 1.x to handle older browsers and fully expect to support it for several more years. It’s easy to use the plugin, just include it in your HTML file after jQuery and open your browser console to see the messages it generates:
If you’re upgrading from a version before 1.9, we recommend that you use the jQuery Migrate plugin and read the jQuery 1.9 Upgrade Guide, since there have been a lot of changes.
Also remember that production web sites should be requesting a specific version from any CDN using a non-specific version like /2/ or jquery-latest.js is considered harmful to your web site’s health and performance. The files should also be available on the Google and Microsoft CDNs soon, but please give these folks a few days before releasing a storm of impatient tweets. The final jQuery 2.0.0 files can be found here on the jQuery CDN: You can (and should) continue to use jQuery 1.9 (and the upcoming 1.10) on web sites that need to accommodate older browsers. But don’t worry, the jQuery team still supports the 1.x branch which does run on IE 6/7/8. In return it is smaller, faster, and can be used in JavaScript environments where the code needed for old-IE compatibility often causes problems of its own. You asked for it, you got it: jQuery 2.0 has arrived!Īs promised, this version leaves behind the older Internet Explorer 6, 7, and 8 browsers.