Earlier this week the jQuery CDN had an issue that made the jquery-latest.js and jquery-latest.min.js files unavailable for a few hours in some geographical areas. (This wasn’t a problem with the CDN itself, but with the repository that provides files for the CDN.) While we always hope to have 100% uptime, this particular outage emphasized the number of production sites following the antipattern of using this file. So let’s be clear: Don’t use jquery-latest.js on a production site.

We know that jquery-latest.js is abused because of the CDN statistics showing it’s the most popular file. That wouldn’t be the case if it was only being used by developers to make a local copy. The jquery-latest.js and jquery-latest.min.js files were meant to provide a simple way to download the latest released version of jQuery core. Instead, some developers include this version directly in their production sites, exposing users to the risk of a broken site each time a new version of jQuery is released. The team tries to minimize those risks, of course, but the jQuery ecosystem is so large that we can’t possibly check it all before making a new release.

To mitigate the risk of “breaking the web”, the jQuery team decided back in 2013 that jquery-latest.js could not be upgraded to the 2.0 branch even though that is technically the latest version. There would just be too many sites that would mysteriously stop working with older versions of Internet Explorer, and many of those sites may not be maintained today.

As jQuery adoption has continued to grow, even that safeguard seems insufficient to protect against careless use of http://code.jquery.com/jquery-latest.js. So we have decided to stop updating this file, as well as the minified copy, keeping both files at version 1.11.1 forever. The latest released version is always available through either the jQuery core download page or the CDN home page. Developers can download the latest version from one of those pages or reference it in a script tag directly from the jQuery CDN by version number.

The Google CDN team has joined us in this effort to prevent inadvertent web breakage and no longer updates the file at http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.js. That file will stay locked at version 1.11.1 as well. However, note that this file currently has a very short cache time, which means you’re losing the performance benefit of of a long cache time that the CDN provides when you request a full version like 1.11.1 instead.

So please spread the word! If you see a site directly using the jQuery CDN’s jquery-latest.js or the Google CDN equivalent in their script tags, let them know they should change to a specific version. If you need the latest version, get it from the download page or our CDN page. For both the jQuery and Google CDNs, always provide a full version number when referencing files in a <script> tag. Thanks!

Ah, the air is sweet with the scent of spring and new jQuery 1.11.1 and 2.1.1 are in bloom. These are minor patch releases and shouldn’t pose any major compatibility issues. Throw a Cinco de Mayo party and have your friends come over to test. If you dig up a problem, let us know at bugs.jquery.com, and be sure to provide a simple test case using jsfiddle.net or jsbin.com to demonstrate the problem.

You can include these files directly from the jQuery CDN if you like, or copy them to your own local server. The 1.x branch includes support for IE 6/7/8 and the 2.x branch does not.

http://code.jquery.com/jquery-1.11.1.js
http://code.jquery.com/jquery-2.1.1.js

The Google and Microsoft CDNs will be getting their copies today just like you did, so please give them a few days to post the files and don’t be impatient. If you’re anxious to get a quick start, just use the files on our CDN until they have a chance to post.

Minified files (for production use) and map files (for debugging) are also available. If you want to use the map file for debugging the minified code, copy the minified file and add a //# sourceMappingURL comment to the end of the file.
http://code.jquery.com/jquery-1.11.1.min.js
http://code.jquery.com/jquery-1.11.1.min.map
http://code.jquery.com/jquery-2.1.1.min.js
http://code.jquery.com/jquery-2.1.1.min.map

Many thanks to all of you who participated in this release by testing, reporting bugs, or submitting patches, including Benjy Cui, Christian Kosmowski, Jason Frank, Julian Aubourg, Jens Simon, John Hoven, John Madhavan-Reese, Jonathan Sampson, Jörn Zaefferer, Leo Balter, Louis-Rémi Babé, Michał Gołębiowski, Oleg Gaidarenko, Philip Jägenstedt, R.G. Otten, Rhys Evans, Richard Gibson, Rick Waldron, Rob Graeber, Rodrigo Rosas, Roman Reiß, S. Andrew Sheppard, Scott González, and Timmy Willison.

Here are the changes since the last official releases (1.11.0 and 2.1.0):

Common to jQuery 1.11.1 and 2.1.1

Ajax

• #14773: load() with selector doesn’t work

Attributes

• #14858: jQuery 1.11.0 and up – .val() of option with no value attribute returning white-space

Build

• #14798: Define bower.json#main for all tags
• #14859: Custom Build: custom AMD name doesn’t work
• #14917: 1.8.3+1 missing jquery.js
• #15020: npm install from git master fails

Core

• #14179: $.isNumeric returns true if argument is an array that contains one integer
• #14687: note on AMD best practices
• #14785: Broken again when transforming XHTML to XHTML (creating XML-DOM) via clientside XSLT
• #14802: User defined onready function on the window is triggered when jQuery is present on the page
• #14882: document.ready doesn’t fire in iOS7 for jQuery loaded after window load event fires

Css

• #14750: $.show() after $.hide() sometimes does not restore the correct display style
• #14792: Inconsistent .css(‘font-weight’) return values
• #14888: Add flexbox properties to jQuery.cssNumber to avoid adding “px”
• #15016: Chrome 34 returns ‘auto’ via getComputedStyle when ‘widows’ property is set to 0

Data

• #14894: IE11: exception when calling $.fn.data() on the body element when it has an ‘onpageshow’ attribute

Dimensions

• #14979: Order of conditions causes unnecessary Reflow

Effects

• #14824: jQuery v1.11 and v2.1 slideUp and slideDown not respecting css display property on non-block elements

Event

• #13997: stopImmediatePropagation doesn’t stop DOM added event listeners
• #14741: Improve compatibility with Pointer Events
• #14791: Triggering beforeunload throws exception

Misc

• #14818: Remove integration tests for Sizzle

jQuery 2.1.1

Ajax

• #14683: ajax: Exceptions thrown synchronously by xhr.send are not caught

Attributes

• #14756: Simplify an option hook

Core

• #14746: Remove special case try/catch in isPlainObject
• #14794: String.prototype.trim doesn’t trim Unicode whitespaces in Android <4.1

Css

• #14836: Css -webkit-transistion, transition not set under Chrome

Event

• #14897: Android 2.3 doesn’t pass isDefaultPrevented value to bubbled events

Manipulation

• #14659: Avoid use of Object.keys() in cleanData()

Selector

• #14902: Use element.matches in alternate selector engine if it’s available

Support

• #14901: “Unsafe HTML” warnings in WWA

jQuery 1.11.1

Css

• #14731: Checking .css(‘marginRight’) after width() can give incorrect results
• #14759: IE8 element.css({ font: ‘bold 11px/14px Lucida Grande’ }) doesn’t work

Spring has sprung, and these release candidates for jQuery 1.11.1 and 2.1.1 are in full bloom. You know what that means? It’s time to get serious about testing! We really want our next release to be solid and reliable, and to do that we need your help. Please try out these files in your projects and pages, just a quick test would be appreciated. If you unearth any problems, let us know at bugs.jquery.com.

The beta files are located on the jQuery CDN, you can include them directly from the CDN if you like (but don’t use them in production!). As always, the 1.x branch includes support for IE 6/7/8 and the 2.x branch does not:

http://code.jquery.com/jquery-1.11.1-rc2.js
http://code.jquery.com/jquery-2.1.1-rc2.js

Here are the bugs fixed since the last official release (1.11.0 and 2.1.0):

Common to jQuery 1.11.1 RC2 and 2.1.1 RC2

Ajax

• #14773: load() with selector doesn’t work

Attributes

• #14858: jQuery 1.11.0 and up – .val() of option with no value attribute returning white-space

Build

• #14798: Define bower.json#main for all tags
• #14859: Custom Build: custom AMD name doesn’t work
• #14917: 1.8.3+1 missing jquery.js
• #15020: npm install from git master fails

Core

• #14179: $.isNumeric returns true if argument is an array that contains one integer
• #14687: note on AMD best practices
• #14802: User defined onready function on the window is triggered when jQuery is present on the page
• #14785: Broken again when transforming XHTML to XHTML (creating XML-DOM) via clientside XSLT
• #14882: document.ready doesn’t fire in iOS7 for jQuery loaded after window load event fires

Css

• #14750: $.show() after $.hide() sometimes does not restore the correct display style
• #14792: Inconsistent .css(‘font-weight’) return values
• #14888: Add flexbox properties to jQuery.cssNumber to avoid adding “px”
• #15016: Chrome 34 returns ‘auto’ via getComputedStyle when ‘widows’ property is set to 0

Dimensions

• #14979: Order of conditions causes unnecessary Reflow

Event

• #13997: stopImmediatePropagation doesn’t stop DOM added event listeners
• #14741: Improve compatibility with Pointer Events
• #14791: Triggering beforeunload throws exception

Misc

• #14818: Remove integration tests for Sizzle

jQuery 1.11.1 RC2

Css

• #14731: Checking .css(‘marginRight’) after width() can give incorrect results
• #14759: IE8 element.css({ font: ‘bold 11px/14px Lucida Grande’ }) doesn’t work

jQuery 2.1.1 RC2

Ajax

• #14683: ajax: Exceptions thrown synchronously by xhr.send are not caught

Attributes

• #14756: Simplify an option hook

Core

• #14746: Remove special case try/catch in isPlainObject
• #14794: String.prototype.trim doesn’t trim Unicode whitespaces in Android <4.1

Css

• #14836: Css -webkit-transistion, transition not set under Chrome

Event

• #14897: Android 2.3 doesn’t pass isDefaultPrevented value to bubbled events

Manipulation

• #14659: Avoid use of Object.keys() in cleanData()

Selector

• #14902: Use element.matches in alternate selector engine if it’s available

With Microsoft ending Windows XP support this month, we’re giving the jQuery community some long-lead-time notice on changes to browser support.

First of all, don’t panic! Nothing is really changing with respect to the browsers that can run jQuery for at least six more months. Our goal is to let everyone in the web development community know what the jQuery team intends to do over the next year, so that you can plan accordingly.

What’s Changing?

There are no firm dates, but we plan on releasing jQuery core versions 1.12 and 2.2 this year. jQuery 1.13/2.3 will be released some time in 2015.

jQuery 1.12: This will be the last release to support Internet Explorer 6 and 7. As of today, no feature requests or bug fixes will be landed for them. Only serious regressions for these browsers will be fixed in patch releases (e.g., 1.12.1). jQuery 1.13 will support IE8 as its minimum browser.

Both jQuery 1.12 and 2.2: These will be the last releases to support Opera 12.1x and Safari 5.1. As of today, no feature requests or bug fixes will be landed for them. Only serious regressions for these browsers will be fixed in patch releases (e.g., 1.12.1 or 2.2.1).

Both jQuery 1.13 and 2.3: We will remove patches and workarounds that are specific to API conformance for the browsers we no longer support, in order to simplify the code base.

What you need to do: If your projects use a package manager that pulls in the latest release of jQuery, keep in mind that the 1.12-to-1.13 or 2.2-to-2.3 upgrade will reduce browser coverage. You may want to stay on 1.12 or lower if support for older browsers is required. See the instructions of your package manager for details on how to do that.

The Meaning of “Support”

Defining what “support” means is trickier than you might think. Under the premise that “untested code is broken code,” the jQuery core team prefers to say we fully support a browser if the project regularly runs unit tests against that browser. The unit tests ensure that every API returns a consistent set of results in all browsers.

Even when we support a browser, there can be bugs we can’t reasonably fix. For example, Internet Explorer 6 through 11 fire focus and blur events asynchronously and the code required to make them appear synchronous would be significant. Safari on iOS doesn’t support the onbeforeunload event which is pretty much impossible to shim. Until last month, Firefox didn’t respect overflow: hidden on a fieldset element. We try to work with browser vendors to get these bugs fixed.

On browsers that we don’t officially support, we still work hard to eliminate “killer bugs” such as script errors during initialization that make the page totally unusable. If you want to see the lengths to which we go to deal with obscure problems, look at this browser-crashing Android 2.3 bug on Japanese phones which was extremely intermittent and hard to diagnose. With the help of several users we were able to track down and work around the problem.

It comes down to this: We can only ensure high-quality continuing support for the browsers and environments we constantly unit-test. However, we will try to provide some reasonable level of support to browsers in any popular environment. The highest priority will be on ensuring the browser doesn’t throw errors. Low priority will be put on ensuring that old or rare browsers produce the exact same API results as modern browsers.

Who Uses Old Browsers Now?

When looking at browser stats, don’t look at where they are today. Think about where they will be in 2015. All told, we think all these browsers will be in the small single digits of market share by then. If numbers from StatCounter can be believed, these browsers are already there and will be even less prevalent when jQuery finally drops support.

Ultimately these whole-Internet stats don’t matter though. What really matters is whether the visitors to your site or users of your web application are running a particular browser. That is something that only you can answer. The decision to upgrade to a new jQuery version is always in your hands as a developer.

The Myth of Browser Consistency

Today and long into the future, jQuery will still contain dozens of browser-specific fixes to normalize behavior. At this point, the most problematic and troublesome browser for jQuery 2.x is the one in Android 2.3. That version is still a significant 20 percent of the Android installed base, and still being shipped in new mobile products. Several JavaScript features like element.classList are not supported there, and it’s one of the last browsers to still require -webkit-prefixing for standardized CSS properties.

jQuery projects are all about making your development life easier, so we’ll continue to support the fixes that are needed to smooth out inconsistencies on popular browsers. As the market share of specific browsers dwindles to zero, we’ll take the opportunity to remove their patches and de-support them in order to streamline our code bases. That makes all jQuery pages a little bit faster.

It’s been a couple of months since our last releases escaped the grip of endless winter, so we thought it would be good to thaw out a beta that collects up the bugs that have been reported and fixed recently. Most of these bugs are mild as severity and frequency go, but that’s easier to say if you’re not impacted!

As with all our beta releases, we make them available so you can test against them and let us know if they fix the bugs without introducing new bugs, surprising behaviors, or regressions. Please help us out by dropping these files into your projects and pages for a quick spin. If you discover any undesirable changes, let us know at bugs.jquery.com.

The beta files are located on the jQuery CDN, you can include them directly from the CDN if you like (but don’t use them in production!). As always, the 1.x branch includes support for IE 6/7/8 and the 2.x branch does not:

http://code.jquery.com/jquery-1.11.1-beta1.js
http://code.jquery.com/jquery-2.1.1-beta1.js

Here are the bugs addressed by these releases:

Common to 1.11.1/2.1.1 Beta 1

Ajax

• #14773: load() with selector doesn’t work

Attributes

• #14858: jQuery 1.11.0 and up – .val() of option with no value attribute returning white-space

Build

• #14798: Define bower.json#main for all tags
• #14859: Custom Build: custom AMD name doesn’t work

Core

• #14179: $.isNumeric returns true if argument is an array that contains one integer
• #14687: note on AMD best practices
• #14802: User defined onready function on the window is triggered when jQuery is present on the page
• #14882: document.ready doesn’t fire in iOS7 for jQuery loaded after window load event fires

Css

• #14750: $.show() after $.hide() sometimes does not restore the correct display style
• #14792: Inconsistent .css(‘font-weight’) return values
• #14888: Add flexbox properties to jQuery.cssNumber to avoid adding “px”

Event

• #13997: stopImmediatePropagation doesn’t stop DOM added event listenders
• #14741: Improve compatibility with Pointer Events
• #14791: Triggering beforeunload throws exception

Unfiled

• #14785: Broken again when transforming XHTML to XHTML (creating XML-DOM) via clientside XSLT

jQuery 1.11.1 Beta 1

Css

• #14731: Checking .css(‘marginRight’) after width() can give incorrect results
• #14759: IE8 element.css({ font: ‘bold 11px/14px Lucida Grande’ }) doesn’t work

jQuery 2.1.1 Beta 1

Ajax

• #14683: ajax: Exceptions thrown synchronously by xhr.send are not caught

Attributes

• #14756: Simplify an option hook

Core

• #14746: Remove special case try/catch in isPlainObject
• #14794: String.prototype.trim doesn’t trim Unicode whitespaces in Android <4.1

Css

• #14836: Css -webkit-transistion, transition not set under Chrome

Event

• #14897: Android 2.3 doesn’t pass isDefaultPrevented value to bubbled events

Manipulation

• #14659: Avoid use of Object.keys() in cleanData()

Selector

• #14902: Use element.matches in alternate selector engine if it’s available

Support

• #14901: “Unsafe HTML” warnings in WWA

Here in the eastern part of the United States, we’re huddling in subzero temperatures and dealing with the aftermath of a snowstorm. Still, there’s nothing to brighten our moods like the pristine beauty of a freshly fallen release–no, make that TWO releases. jQuery 1.11.0 and 2.1.0 are ready to keep you warm on these dark winter nights.

You can get the files off our CDN as always, and either use them directly or download them to your own server. Our download page has all the files and information you need, including pointers to the other CDNs that carry the files. Just give those folks a few days to update!

For those of you not following along for a while, both the 1.x and 2.x branches of jQuery support all recent modern browsers and have the same API. The 1.x branch, this time 1.11.0, adds support for the older versions of Internet Explorer (IE6, 7, and 8). The 2.x branch, today played by 2.1.0, adds support for non-traditional web environments like node.js and browser plugins for Chrome and Firefox.

jQuery went through a major house-cleaning with the 1.9 release that removed some features. If you haven’t yet moved from an earlier version, see the jQuery 1.9 Upgrade Guide and let the jQuery Migrate plugin do all the heavy lifting for you.

What’s New?

You may be wondering what great new things await you in these releases. Perhaps you’re fearing that they hold a bunch of breaking changes. You just know the project lead will suggest updating things right now. There goes your whole damn week and that trip to Florida. Well fear not! We’ve fixed quite a few bugs, but the other features and changes are mainly organizational ones that don’t affect the behavior of APIs. Your code shouldn’t break, it should just run a little faster. Here are the highlights:

Fewer forced layouts: In this release we declared war on places where we might inadvertently force the browser to do a time-consuming layout. We found a few and eliminated one in particular that could occur when changing class names. This can result in a big performance boost for some pages.

Granular custom builds: Our modularity is now defined by AMD, and it is easier to build small subsets of the library when space is at a premium. If you want to know more, we’ve hidden the details in the README file where nobody ever looks.

Lower startup overhead: The new modularity and avoidance of forced layouts led us to refactor our feature detects so that they run the first time they’re needed. If you never call the API needing that feature detect, you never run that code. Previously we ran all feature detects when the page loaded, that led to delays that were generally small, but added up–especially on mobile platforms.

Published on npm: Our releases will now be published on npm so that you can use them with node or browserify. Both the 1.x and 2.x branches are available on npm, but remember that only the 2.x branch is supported to run in node.

Published on Bower: We’re now using Bower for our internal dependency management including Sizzle, so you’ll see jQuery releases on Bower as soon as they’re available.

Some people have asked about supporting other package managers inside the jQuery library, but we’ve decided to only support the two that we use internally at the moment. There are more than a dozen package/dependency managers, it would be handy if they all could agree on a single format for projects to publish information. We don’t want the package manager’s overhead to be pushed off to individual projects like jQuery.

Although the glamor always seems to be in the new stuff, we don’t like to ignore the bugs and inconveniences that people have run across while using the last version. We worked hard to knock down our bug list and tackled quite a few of them. We even fixed a bug that only occurs in IE6, better late than never!

Sourcemap changes

This release does not contain the sourcemap comment in the minified file. Sourcemaps have proven to be a very problematic and puzzling thing to developers, spawning hundreds of confused developers on forums like StackOverflow and causing some to think jQuery itself was broken.

We’ll still be generating and distributing sourcemaps, but you will need to add the appropriate sourcemap comment at the end of the minified file if the browser does not support manually associating map files (currently, none do). If you generate your own jQuery file using the custom build process, the sourcemap comment will be present in the minified file and the map is generated; you can either leave it in and use sourcemaps or edit it out and ignore the map file entirely.

We hope to bring back and improve sourcemap support in the future, but at the moment neither the design nor the implementation seem suited for situations like jQuery’s, where there are widely distributed files on CDNs. We’d like sourcemaps (and browsers supporting them) to gracefully handle situations like file renaming or missing files. See our bug ticket for more information.

Acknowledgements

This release would not have happened without the hard work of many people. Thanks to everyone who reported bugs, tried out the prerelease files, or provided constructive criticism. Particular thanks are due to Alex Robbin, Amey Sakhadeo, Anthony Ryan, Aurelio DeRosa, Chris Antaki, Chris Price, Christopher Jones, Corey Frang, Daniel Herman, Domenic Denicola, Dominik D. Geyer, Forbes Lindesay, George Kats, Guy Bedford, Ilya Kantor, Jakob Stoeck, Jeremy Dunck, John Paul, Julian Aubourg, Jörn Zaefferer, Lihan Li, Marian Sollmann, Markus Staab, Marlon Landaverde, Michał Gołębiowski, Mike Sidorov, Oleg Gaidarenko, Richard Gibson, Rick Waldron, Ronny Springer, Scott González, Sindre Sorhus, T.J. Crowder, Terry Jones, Timmy Willison, and Timo Tijhof. Colin Snover’s commentary in #jquery-dev is also a source of rare humor for the team.

Changelog

jQuery 1.11 and 2.1 (common to both)

Ajax

• #14036: ajaxLocation Includes HTTP Basic Authentication Info
• #14356: Remove string indexing used in AJAX
• #14379: Issue with xhr.js

Attributes

• #14250: addClass and removeClass needlessly assign to className.

Build

• #12757: Enforce style guide via build process
• #13983: Switch to //# for sourcemap directives
• #14016: Include a build option for customizing exports
• #14113: AMD-ify jQuery source
• #14118: Use bower to include Sizzle and QUnit (remove submodules)
• #14163: Make Deferreds/Callbacks/.ready() optional modules
• #14415: Remove sourcemap comment
• #14450: Remove CommonJS+AMD syntax from source
• #14451: Add bower and npm registrations to release script
• #14504: Build: Upgrade to grunt-contrib-jshint 0.7.1 and squash subtasks
• #14615: Manage bower dependencies with grunt-bowercopy
• #14702: Problem with npm package for jquery ‘latest’

Core

• #14164: Reduce forced layout reflows in init or methods
• #14492: parseJSON incorrectly accepts comma expressions
• #14548: npm jQuery does not have a main module
• #14549: npm jQuery does not expose the jQuery function, but instead a wierd factory
• #14645: Remove global exposure for CommonJS environments with a document

Css

• #14150: IE9-10 curCSS => “Interface not supported” in for popups (and probably frames)
• #14394: style=”x: y !important;” doesn’t get changed when calling el.css(x, z) in Chrome and Safari but it works in Firefox

Data

• #14101: Version 1.10 .data() differs from 1.8 when getting data from non-existent object
• #14459: data-* attribute parsing bypasses jQuery.parseJSON (inconsistent with 1.x)

Effects

• #14344: Putting different effects in callbacks uses only the first effect.

Event

• #13993: .triggerHandler doesn’t return value from handler for DOM0 events
• #14180: focusin/out special events don’t work cross-window
• #14282: Don’t call getPreventDefault() if there is a defaultPrevented property

Manipulation

• #14716: Textarea isn’t cloned properly in IE11

Misc

• #14040: Tests: Replace QUnit.reset usage

Selector

• #14142: Wrong number of elements returned in XML document with numeric IDs in Safari
• #14351: Exception thrown when running `find` in a non-attached DOM node
• #14381: .add() throws “no such interface” in IE when adding nodes from another window
• #14535: Selection fails in IE11 when the last context is a no-longer-present iframe document
• #14584: Attribute Ends With case-insensitive in some IE8

Support

• #10814: make support as lazy as possible with closure in mind
• #14084: elem.css(‘width’) provides incorrect output with `box-sizing: border-box` if run before document ready
• #14401: Error when loading a page with application/xhtml+xml
• #14496: jQuery 2.1.0-beta1 fails to initialize in a XHTML page

jQuery 1.11

Ajax

• #13240: IE8 Doesn’t support HTTP PATCH method
• #14475: Local Ajax requests don’t work in IE 11 (ActiveXObject checking in jQuery fails)

Attributes

• #2252: Setting select value via val() shows error in IE6

Build

• #14663: jQuery 1.11.0-beta3 on npm

Core

• #14074: jQuery 1 throws an error on window ready when there is an element in the DOM with the id ‘nodeName’

Effects

• #14318: The animations fadeIn and fadeOut do to function as expected when used with stop()

Support

• #14422: CSP violation including jquery in a blank page

jQuery 2.1

Ajax

• #14207: Ajax error defaults to status 404

Build

• #13119: Make jQuery releases available via npm
• #13768: Error trying to load jQuery from node.js
• #14340: Remove oldIE code from support tests on master

Core

• #14313: Optimize jQuery.merge for size

Event

• #14544: Remove elem reference from event handler