As part of its ongoing infrastructure updates, the jQuery infrastructure team is making configuration and deployment changes to address intermittent outages reported by some users. The issue is the result of faulty IP allowlisting which affects users downloading jQuery project assets from certain IP addresses.

This issue is expected to be resolved in the next few weeks. In the interim, users can mitigate the issue by downloading and serving the files they need.

CDN migration is part of a package of infrastructure improvement projects the project has been undertaking this year. The infrastructure team plans to provide a full overview of these improvements, which will help support the long-term maintenance of jQuery and its related projects, later this summer.

jQuery continues to be a widely-used open source project with active maintainers. While many sites host jQuery locally, others rely upon the jQuery CDN to deliver the library on demand. On average, the jQuery CDN delivers over 2 petabytes of code per month. The project is hosted at the OpenJS Foundation, the vendor-neutral organization to grow and sustain the JavaScript and web ecosystem.

jQuery has a new release! It’s been a while since our last release, but we expect this to be the last minor release in the 3.x branch, and then we will move on to the overhaul that will be jQuery 4.0. But before we get to 4.0, we’re excited to share the bug fixes and improvements included in jQuery 3.4.0. Here are some of the highlights:

Performance improvement in .width and .height

When getting and setting dimensions, there were certain cases where this could cause layout thrashing, which basically means that the browser calculated layout more times than necessary. We fixed this in all browsers except IE, where it can’t be avoided.

nonce and nomodule support

To support adding script elements through methods like .html and .append, jQuery separates them and appends new script tags to load and execute the remote content. During this process, attributes such as nonce and nomodule were ignored, but jQuery 3.4.0 now hangs onto them.

Radio elements: expected state in event handlers

We had already fixed the same issue with checkboxes, but accidentally left out radio inputs. In the following example, true was logged the first time the element was clicked. We fixed it so that the checked property is updated before the event handler is executed.

Example

var $radios = jQuery(".example");
var $firstRadio = $radios.first();
var firstCheckedState = $firstRadio.prop("checked");
$radio.on("click", function() {
  // true in <3.4.0
  console.log($firstRadio.prop("checked") === firstCheckedState);
});
$radios.eq(1).click();

Minor vulnerability fix: Object.prototype pollution

jQuery 3.4.0 includes a fix for some unintended behavior when using jQuery.extend(true, {}, ...). If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype. This fix is included in jQuery 3.4.0, but patch diffs exist to patch previous jQuery versions.

Example

jQuery.extend(true, {},
  JSON.parse('{"__proto__": {"test": true}}')
);
console.log( "test" in {} ); // true

Note that while jQuery does its best to protect users from security vulnerabilities, jQuery is a DOM manipulation library that will generally do what you tell it to do. In this case, the behavior was likely unexpected, so jQuery.extend will no longer write any properties named __proto__. But guards such as this one are not replacements for good security practices such as user input sanitization.

Deprecating positional selectors and the sunset of Sizzle

The basic API of jQuery is to select something and then do something with what was selected. Sizzle, the selector engine in jQuery, handles the first half. It’s been a fast and efficient little engine that has paved the way for native selector APIs like querySelectorAll and additional native JavaScript and CSS selectors. Now that many of these selectors have made their way into modern browsers, it’s almost time to say goodbye to Sizzle. But in order to remove Sizzle in jQuery 4.0, we will also need to remove what we refer to as positional selectors, which are non-standard selectors.

Specifically, jQuery 3.4.0 is deprecating :first, :last, :eq, :even, :odd, :lt, :gt, and :nth. When we remove Sizzle, we’ll replace it with a small wrapper around querySelectorAll, and it would be almost impossible to reimplement these selectors without a larger selector engine.

We think this trade-off is worth it. Keep in mind we will still support the positional methods, such as .first, .last, and .eq. Anything you can do with positional selectors, you can do with positional methods instead. They perform better anyway.

Upgrading

There should be no compatibility issues if upgrading from jQuery 3.0+. If you haven’t yet upgraded to jQuery 3+, please have a look at the 3.0 Upgrade Guide. The jQuery Migrate 3.0 plugin will help you to identify compatibility issues in your code.

Please try out this new release and let us know about any issues you experienced.

Download

You can get the files from the jQuery CDN, or link to them directly:

https://code.jquery.com/jquery-3.4.0.js

https://code.jquery.com/jquery-3.4.0.min.js

You can also get this release from npm:

npm install jquery@3.4.0

Slim build

Sometimes you don’t need ajax, or you prefer to use one of the many standalone libraries that focus on ajax requests. And often it is simpler to use a combination of CSS and class manipulation for web animations. Along with the regular version of jQuery that includes the ajax and effects modules, we’ve released a “slim” version that excludes these modules. The size of jQuery is very rarely a load performance concern these days, but the slim build is about 6k gzipped bytes smaller than the regular version. These files are also available in the npm package and on the CDN:

https://code.jquery.com/jquery-3.4.0.slim.js

https://code.jquery.com/jquery-3.4.0.slim.min.js

These updates are already available as the current versions on npm and Bower. Information on all the ways to get jQuery is available at https://jquery.com/download/. Public CDNs receive their copies today, please give them a few days to post the files. If you’re anxious to get a quick start, use the files on our CDN until they have a chance to update.

Thanks

Thank you to all of you who participated in this release by submitting patches, reporting bugs, or testing, including abnud1, Jason Bedard, buddh4, Kris Borchers, Andrei Fangli, Oleg Gaidarenko, Richard Gibson, Michal Golebiowski-Owczarek, Marja Hölttä, Dave Methvin, Ed S, Luis Emilio Velasco Sanchez, Saptak Sengupta, tmybr11, Bert Zhang, and the whole jQuery team.

Changelog

GitHub changelog: Issues fixed in 3.4.0 | All changes

Ajax

• Allow custom attributes when script transport is used (#3028, 1f4375a3)
• Fix getResponseHeader(key) for IE11 (#3403, e0d94115)

Core

• Use isAttached to check for attachment of element (662083ed)
• Tiny efficiency fix to jQuery.extend / jQuery.fn.extend (#4246) (#4245, 4ffb1df8)
• Preserve CSP nonce on scripts with src attribute in DOM manipulation (#4323, 00504037)
• Preserve CSP nonce on scripts in DOM manipulation (#3541, c7c2855e)
• Support passing nonce through jQuery.globalEval (#4278, 5bdc85b8)
• Recognize Shadow DOM in attachment checks (#3504, 9b77def5)
• Prevent Object.prototype pollution for $.extend( true, … ) (753d591a)

CSS

• Ensure camel- vs kebab-cased names are not collapsed for CSS vars (f8c1e902)
• Avoid filling jQuery.cssProps (#3986, 2b5f5d5e)
• Correctly detect scrollbox support with non-default zoom (#4029, 821bf343)
• Don’t auto-append “px” to CSS variables (#4064) (#4063, 75b77b48)
• Skip the px-appending logic for animations of non-element props (f5e36bd8)
• Avoid forcing a reflow in width/height getters unless necessary (#4322, a0abd15b)
• Don’t read styles.position in the width/height cssHook unless necessary (#4185, 354f6036)
• Don’t auto-append “px” to possibly-unitless CSS grid properties (#4007, f997241f)

Dimensions

• fix computing outerWidth on SVGs (#3964, e743cbd2)
• avoid fetching boxSizing when setting width/height – this avoids forcing a reflow in some cases (#3991, 73d7e625)
• fall back to offsetWidth/Height for border-box in IE (#4102, 315199c1)

Event

• Prevent leverageNative from double-firing focusin (fe5f04de)
• Add “code” property to Event object (#3978, 899c56f6)
• Leverage native events for focus/blur/click; propagate additional data (#1741, #3423, #3751, #4139, 669f720e)
• Respect script nomodule attribute in DOM manipulation (#4281, e4de8b46)
• Restore _evalUrl jQuery.ajax calls to dataType: script (13de7c9e)
• Only evaluate HTTP-successful script src (#4126, c2026b11)

Manipulation

• Properly detect HTML elements with single-character names (#4124, 979809c5)

Misc

• Add config for lockbot (2348f399)
• Update license prolog/epilog to placate Github checker (29e76e25)

README

• add gitter badge to README.md (7869f83d)
• Add FOSSA license scan status badge (45f08588)

Selector

• Update Sizzle from 2.3.3 to 2.3.4 (#1756, #4170, #4249, d940bc06)

Serialize

• jQuery.param: return empty string when given null/undefined (#2633, 0645099e)

Traversing

• $.fn.contents() support for object (#4045, 0ba8e38d)

Internal

• Seasonal update of uglify and its options (09684ba3)
• Remove unnecessary ESLint exception (dc05f3c1)
• Run the basic test suite in jsdom (0ec25abb)
• Remove manual QUnit fixture resetting (84b6a0be)
• Make Promises/A+ tests use the dot reporter instead of the default (ca9356ec)
• Update QUnit from 1.23.1 to 2.9.2 (6ced2639)
• Run Karma browser tests on Node.js 10 instead of 8 (16ad9889)
• Update jsdom; migrate a test with Symbol polyfill to an iframe test (9cb124ed)
• Remove obsolete globals from ESLint configuration (c10945d0)
• Update most dependencies (8751e9ef)
• Update test code for compatibility with QUnit 2.x (#4297) (c3498187)
• Advise to create test cases on JS Bin or CodePen, drop JSFiddle (da44ff39)

Quite a while back, Mike Taylor pointed out that the jQuery CDN has a minified copy of jQuery 1.9.1 with an incorrect map file reference. Basically, it refers to the map for jQuery 1.11.1, and that’s just wrong. If you are trying to debug a site that uses the minified jQuery 1.9.1 file, dev tools will get very confused and make a hard job even harder.

You might think that we could just edit the https://code.jquery.com/jquery-1.9.1.min.js file to point to the correct map file, which does exist as https://code.jquery.com/jquery-1.9.1.min.map. There are at least two problems with doing that. The first is that the file is heavily cached across the internet, since it’s been assumed for years that it will never change once the release occurs. Even if we edited the file, both the JavaScript and map file might never actually update at the point where they’re being used.

A second problem is even more serious. We’ve been advocating that developers use the script’s integrity attribute to ensure that the file you are including has not been modified since you originally wrote the script tag. If we modify the contents of the file this attribute will be wrong and the page will no longer include the file. This is likely to completely break the page! Given the age of jQuery 1.9.1 it is possible that many of the pages including this file are not being actively maintained. Thus, we can’t seriously consider changing the JavaScript file in any way, not even one byte.

The least disruptive option is to remove the jquery.min.map file that the jQuery 1.9.1 minified file references. It does not affect whether jQuery runs correctly for the visitors of a site. It only has the effect of disabling the source map. Because of these pitfalls of including the sourceMappingURL map reference in CDN JavaScript files that are often copied elsewhere, we no longer include it.

If you need to debug a site using one of these minified files, it is possible to manually associate a map file in Chrome. Open the minified source file, right click over the area of the minified source, and select “Add source map…”.

The incorrect jquery.min.map file has been removed from the jQuery CDN. We expect that there won’t be any observable change from removing this file, other than restoring sanity to debugging a site that uses jQuery 1.9.1. The jQuery 1.11.1 minified file does not reference its map, so it will continue to work fine and you can associate a map file as mentioned above.

Because caches are so aggressive on CDNs and across the internet, it’s possible that you may still see this map file for a while. If you see some unusual behavior that you think is related to the missing jquery.min.map file you can open a ticket on the CDN issue tracker.

We encountered an issue in the release for jQuery 3.3.0, so we’ve immediately released another tag. The code itself is identical, but our release dependencies (only used during release) were added to the dependencies of the jQuery package itself due to the new behavior of npm in version 5+.

jQuery 3.3.1 is now recommended if installing from npm or GitHub. If using jQuery on any CDN, the built file only differs in the version number.

We apologize for any inconvenience and have updated our release script to account for this issue.

Please see the jQuery 3.3.0 blog post for all relevant code changes in this release.

Download

You can get the files from the jQuery CDN, or link to them directly:

https://code.jquery.com/jquery-3.3.1.js

https://code.jquery.com/jquery-3.3.1.min.js

You can also get this release from npm:

npm install jquery@3.3.1

Slim build

Sometimes you don’t need ajax, or you prefer to use one of the many standalone libraries that focus on ajax requests. And often it is simpler to use a combination of CSS and class manipulation for all your web animations. Along with the regular version of jQuery that includes the ajax and effects modules, we’ve released a “slim” version that excludes these modules. The size of jQuery is very rarely a load performance concern these days, but the slim build is about 6k gzipped bytes smaller than the regular version – 24k vs 30k. These files are also available in the npm package and on the CDN:

https://code.jquery.com/jquery-3.3.1.slim.js
https://code.jquery.com/jquery-3.3.1.slim.min.js

These updates are already available as the current versions on npm and Bower. Information on all the ways to get jQuery is available at https://jquery.com/download/. Public CDNs receive their copies today, please give them a few days to post the files. If you’re anxious to get a quick start, use the files on our CDN until they have a chance to update.

It’s been a while since the last jQuery release, but the Core team hasn’t been idle. We’ve got an all new minor release for you, and it’s even got a new feature in it!

The .addClass(), .removeClass(), and .toggleClass() methods now accept an array of classes.

jQuery(elem).addClass([
   'dave', 'michał', 
   'oleg', 'richard', 
   'jason', 'timmy'
]);

Generally, jQuery is not looking to add anything new. We tend to focus more on what we can remove rather than what we can add. But as soon as we saw this feature request, we wondered how it hadn’t been added before.

There should be no compatibility issues if upgrading from jQuery 3.0+. If you haven’t yet upgraded to jQuery 3+, please have a look at the 3.0 Upgrade Guide. The jQuery Migrate 3.0 plugin will help you to identify compatibility issues in your code.

Please try out this new release and let us know about any issues you experienced.

Deprecations

We’ve pruned some roses, lilies, and sunflowers in this release. Some of these will smell sweeter than others, but put them together, and you’ve got a beautiful bouquet of…depre-carnations.

These functions have either lost some of their usefulness over time, are considered to be less favorable than available alternatives, or were intended for internal usage from the beginning. While most of these will be removed in jQuery 4.0, it’s worth noting that we do not consider the deprecation of a method to mean that it will be removed; it means that we encourage the use of alternatives. For instance, event aliases like .click() will likely never be removed.

• jQuery.now (#2959, 909e0c99)
• jQuery.isWindow (#3629, c18d6085)
• jQuery.camelCase(#3384, 64a28928)
• jQuery.proxy (not slated for removal) (#2958, 3a8e4474)
• jQuery.type (#3605, 1ea092a5)
• jQuery.isNumeric (#2960, c4494d4a)
• jQuery.isFunction (#3609, 3d732cca)
• Event aliases (#3214, 022b69a4)

Command-line Testing

The magnificent Timo Tijhof has made it possible to run all jQuery tests on the command line, using grunt and karma. This is something we’ve always wanted but it was complicated by our need for a php server to run ajax tests. Thanks to Timo for making it happen!

Note: jQuery no longer runs any tests on PhantomJS 1.x.

Download

You can get the files from the jQuery CDN, or link to them directly:

https://code.jquery.com/jquery-3.3.0.js

https://code.jquery.com/jquery-3.3.0.min.js

You can also get this release from npm:

npm install jquery@3.3.0

Slim build

Sometimes you don’t need ajax, or you prefer to use one of the many standalone libraries that focus on ajax requests. And often it is simpler to use a combination of CSS and class manipulation for all your web animations. Along with the regular version of jQuery that includes the ajax and effects modules, we’ve released a “slim” version that excludes these modules. The size of jQuery is very rarely a load performance concern these days, but the slim build is about 6k gzipped bytes smaller than the regular version – 24k vs 30k. These files are also available in the npm package and on the CDN:

https://code.jquery.com/jquery-3.3.0.slim.js
https://code.jquery.com/jquery-3.3.0.slim.min.js

These updates are already available as the current versions on npm and Bower. Information on all the ways to get jQuery is available at https://jquery.com/download/. Public CDNs receive their copies today, please give them a few days to post the files. If you’re anxious to get a quick start, use the files on our CDN until they have a chance to update.

Thanks

Thank you to all of you who participated in this release by submitting patches, reporting bugs, or testing, including Andreas Solledar, Basil Belokon, Boom Lee, “CDAGaming”, Dave Methvin, Erik Lax, Henry Zhu, Jason Bedard, Jordan Beland, Matan Kotler-Berkowitz, Michał Gołębiowski-Owczarek, Nilton Cesar, Pierre Spring, Richard Gibson, Saptak Sengupta, Shashanka Nataraj, Steve Mao, Timo Tijhof, Faisal Irfan Yar Khan, and the whole jQuery team.

 

Changelog

GitHub changelog: Issues fixed in 3.3.0 | All changes

Ajax

• Add an ontimeout handler to all requests (#3586, 262acc6f)
• Don’t process non-string data property on no-entity-body requests (#3438, d7237896)

Attributes

• Feature: Allow array param in add/remove/toggleClass (#3532, 80f57f8a)

Build

• Test on Node.js 8, stop testing on Node.js 7 (bef46a2a)
• Update to Babel 7, use for-of plugin instead of preset-es2015 (90bac40a)
• Remove package-lock.json, add it to .gitignore (#3792, 7037facc)
• Test on Node.js 9 (3e902a81)
• Fix UglifyJS output in Android 4.0; update uglify (#3743, c9efd11f)

Core

• Deprecate jQuery.now (#2959, 909e0c99)
• Deprecate jQuery.isWindow (#3629, c18d6085)
• Make camelCase function available only for internal usage (#3384, 64a28928)
• Deprecate jQuery.proxy (not slated for removal) (#2958, 3a8e4474)
• Deprecate jQuery.type (#3605, 1ea092a5)
• Deprecate jQuery.isNumeric (#2960, c4494d4a)
• Update isFunction to handle unusual-@@toStringTag input (#3600, #3596, a16339b8)
• Deprecate jQuery.isFunction (#3609, 3d732cca)

CSS

• Drop the float mapping from cssProps (bbf33428)
• Correctly set support properties with non-default zoom (#3808, f00a0759)
• Detect more WebKit styles erroneously reported as percentages (#3777, 94ddf620)
• Retrieve inline style before computed (c4598da4)
• Avoid unit-conversion interference from CSS upper bounds (#2144, 692f9d4d)

Deferred

• Fix memory leak of promise callbacks (#3606, 36389288)

Dimensions

• Improve offsetWidth/offsetHeight fallback (#3698, #3602, a4957849)
• Include scroll gutter in “padding” box (#3589, 80f1c823)
• Fall back to offsetWidth/Height for inline elems (#3571, 473d2ea7)
• Don’t trust non-pixel computed width/height (#3611, 3cf1d14c)
• Detect and account for content-box dimension mishandling (#3699, 3fcddd6e)

Docs

• Create CODE_OF_CONDUCT.md (e84d3bc0)
• Update links to HTML spec for stripAndCollapse (#3594) (e1b1b2d7)

Event

• Move event aliases to deprecated (#3214, 022b69a4)
• `stopPropagation()` on native event-handler (#3693, 490db839)

Filter

• Use direct filter in winnow (#3272, 4765bb5c)

Manipulation

• Use `.children` to select tbody elements (a88b48ea)
• Add support for scripts with module type (#3871, 5d3a968e)

Offset

• Use correct offset parents; include all border/scroll values (#3080, #3107, 1d2df772)

Support

• Properly check for IE9 absolute scrollbox mishandling (#3699, #3730, 20cdf4e7)