"); +$div.data("clickCount", 2); +$div.data("clickCount"); // 2 +$div.data("click-count", 3); +$div.data("clickCount"); // 3 +$div.data("click-count"); // 3 + +var allData = $div.data(); +allData.clickCount; // 3 +allData["click-count"]; // undefined +allData["click-count"] = 14; +$div.data("click-count"); // 3, NOT 14 as it would be in jQuery 2.x +allData.clickCount; // 3 +allData["click-count"]; // 14 +``` + +https://github.com/jquery/jquery/issues/2070 +https://github.com/jquery/jquery/issues/2257 +https://github.com/jquery/jquery/issues/1751 + +### Deferred + +#### Breaking change and Feature: $.Deferred is now Promise/A+ compatible + +Deferreds have been updated for compatibility with Promise/A+ and ES2015 (a.k.a ES6) Promise. This introduces a `.catch()` method and makes some major changes to the `.then()` method. In particular, any exception thrown within a `.then()` callback now becomes a rejection value and we *strongly recommend* that you add a `.catch()` method to the end of your promise chain to avoid dificult debugging issues. + +The most likely place you may encounter this new behavior is when using the Deferreds that are produced by `jQuery.ajax()`, since the `jQXHR` object it returns is a superset of `$.Deferred`. + +The Promise/A+ spec says that promises are always resolved with a single value and handlers are invoked without a `this` context, while `jQuery.ajax()` sometimes passes context and/or multiple values to its handlers. In most cases, though, the first argument is the most important of these values. If you are currently using a `.then()` you may only receive a single argument in your handler. To get context and/or more arguments, switch to the older `.done()` and `.fail()` methods which retain all the backward-compatible behavior: + +```js +// Typical old uses of .then() that are not Promise/A+ compatible +$.ajax("url").then( + // success + function( data, textStatus, jqXHR ) { /* code */ }, + // error + function( jqXHR, textStatus, errorThrown ) { /* code */ } +); + +// Rewrite to this in order to maintain previous behavior +$.ajax("url") + // success + .done(function( data, textStatus, jqXHR ) { /* code */ }) + // error + .fail(function( jqXHR, textStatus, errorThrown ) { /* code */ }); +``` + +Another behavior change required for Promise/A+ compliance is that Deferred `.then()` callbacks are *always* called asynchronously. Previously, if a `.then()` callback was added to a Deferred that was already resolved or rejected, the callback would run immediately and synchronously. + +Deferred methods such as `.done()`, `.fail()`, and `.pipe()` retain their old behavior and so are not Promise/A+ compliant. If you require synchronous resolution, do not want exceptions converted to rejection values, or want thrown errors to bubble out of the function where they occur, you can use these methods instead of `.then()` and `.catch()`. + +In jQuery 1.x and 2.x, an uncaught exception inside a callback function halts code execution. The thrown exception bubbles up until it is caught inside a try/catch or reaches `window` and triggers `window.onerror`. + +For example, consider this code using the new standard Promise/A behavior: + +```js +$.ajax("/status") + .then(function(data) { + whoops(); + // console shows "jQuery.Deferred exception: whoops is not a function" + // no further code executes in this function + }) + .catch(function(arg) { + // this code executes after the error above + // arg is an Error object, "whoops is not a function" + }); +``` + +Compare that to the old-style Deferred methods: + +```js +$.ajax("/status") + .done(function(data) { + whoops(); + // console shows: "whoops is not a function" + // no further code executes in this function + }) + .fail(function(arg) { + // this code does not execute since the exception was not caught + }); +``` + +Note that jQuery logs a message to the console when it is inside a Deferred and a JavaScript exception occurs. These messages take the form `jQuery.Deferred exception: (error message)`. If you do not want any console output on these exceptions, set `jQuery.Deferred.exceptionHook` to `undefined`. If you need further help in finding errors reported this way, use the [jquery-deferred-reporter plugin](https://github.com/dmethvin/jquery-deferred-reporter) during development to obtain stack traces. + +https://github.com/jquery/jquery/issues/1722 +https://github.com/jquery/jquery/issues/2102 +https://github.com/jquery/jquery/issues/2736 + +#### Breaking change and Feature: $.when() inputs and progress notifications + +The $.when() method now interprets that any input argument with a `.then()` method is a Promise or Deferred compatible object. In previous versions, if a single Deferred was passed as an input argument, `$.when()` would re-use it and return it as the output Deferred. Now, it *always* returns a new Deferred. This allows any type of`then`-able to be passed as input, including native ES6 Promise or Bluebird promises. You can also convert to the output Deferred to an ES6 promise with `Promise.resolve()` where native Promise is supported. + +As of jQuery 3.0, the `$.when()` method no longer passes along progress notifications from input Deferreds to the output Deferred. Progress messages are not part of the Promise/A+ specification, and the behavior of progress notifications in `$.when()` were not previously documented in the jQuery API. + +https://github.com/jquery/jquery/issues/2710 +https://github.com/jquery/jquery/issues/2546 + + +### Dimensions +#### Breaking change: .width(), .height(), .css("width"), and .css("height") can return non-integer values + +Before version 3.0, jQuery used the DOM `offsetWidth` and `offsetHeight` properties to determine the dimensions of an element, and these properties always return integers. With jQuery 3.0 we get more precise values via the DOM `getBoundingClientRect` API, and these may may not be integers. If your code always expects integers for dimensions, it may need to be adjusted to deal with this extra precision. + +https://github.com/jquery/jquery/issues/1724 + + +#### Breaking change: `.outerWidth()` or `.outerHeight()` on `window` includes scrollbar width/height + +Calls to `$(window).width()` return the "content width" which excludes any scrollbars that the browser has added if the content exceeds the height of the element. This is different from the width that CSS uses for media queries, which includes the width of the scrollbars. In order to provide a measure that is equivalent to the CSS media query concept of width, the `$(window).outerWidth()` method now returns the width including scrollbar width. This is equivalent to the DOM property `window.innerWidth`. The same applies for `.outerHeight()`. + +https://github.com/jquery/jquery/issues/1729 + +### Effects + +#### Breaking change: .show(), .hide(), and .toggle() methods now respect more stylesheet changes + +The code that jQuery uses to show and hide elements has been updated to focus on inline rather than computed styles, respecting stylesheet `display` values whenever possible for increased compatibility with responsive design techniques (in which active stylesheet rules can dynamically change upon device reorientation/window resize/etc.). As a result, disconnected elements are no longer considered hidden unless they have inline `display: none`, and therefore `.toggle()` will no longer differentiate them from connected elements as of jQuery 3.0. + +Further, while `.show()` and similar calls will continue to force visibility of elements that are hidden by stylesheet rules, supporting this functionality slows down all show/hide operations and its use is not recommended. The determination of which display value to set in such cases has also been simplified, defaulting to "block" when body-level rules hide elements by type. + +Any code expecting hidden elements to be reshown with their previous _computed_ display styles, or disconnected elements to treated as hidden, should be reviewed. The team created a [table](https://docs.google.com/spreadsheets/d/1UaISjcS3UMxVJ7eSBIXtK-jqF8Grl67w640peCqlkoc/edit) of all the possibilities related to the display state and show/hide actions in order to minimize the setting of non-empty inline styles. + + +**SITUATIONS WHERE THE OUTCOME WILL BE DIFFERENT** +**WHAT USERS NEED TO DO TO FIX IT** + +#### Feature: Animations now use requestAnimationFrame + +On platforms that support the `requestAnimationFrame` API, which is pretty much everywhere but IE9, jQuery will now use that API when performing animations. This should result in animations that are smoother and use less CPU time � and save battery as well on mobile devices. + +jQuery tried using requestAnimationFrame a few years back but there were serious compatibility issues with existing code so we had to back it out. We think we�ve beaten most of those issues by suspending animations while a browser tab is out of view. Still, any code that depends on animations to always run in nearly real-time is making an unrealistic assumption. + +#### Deprecated: Additional easing function parameters + +The easing functions called by `.animate()` are passed single argument, the percentage of completion. Some older code assumes that it is passed additional arguments derived from the percentage. These other arguments may not be present in a future major version update. + +Example of an old easing method: +```js +$.easing.easeInOutSine = function (x, t, b, c, d) { + return -c/2 * (Math.cos(Math.PI*t/d) - 1) + b; +}; +``` +The same easing method rewritten: +```js +$.easing.easeInOutSine = function (x) { + return -0.5*(Math.cos(Math.PI*x) - 1); +}; +``` + +https://github.com/jquery/api.jquery.com/issues/912 + + +### Event + +#### Breaking change: .load(), .unload(), and .error() removed + +These methods are shortcuts for event operations, but had several API limitations. The event `.load()` method conflicted with the ajax `.load()` method. The `.error()` method could not be used with `window.onerror` because of the way the DOM method is defined. If you need to attach errors by these names, use the `.on()` method, e.g. change `$("img").load(fn)` to `$(img).on("load", fn)`. + +https://github.com/jquery/jquery/issues/2286 + +#### Breaking change: `.on("ready", fn)` removed + +jQuery no longer supports a synthetic event named `"ready"` that can be used with the event functions. This event was error-prone and deprecated in jQuery 1.8 because it would only call the callback if it was attached before the document was ready. Replace any uses with `$(fn)` instead, which works reliably. + +https://github.com/jquery/jquery/issues/2264 + +#### Deprecated: .bind() and .delegate() + +Five years ago in jQuery 1.7 we introduced the `.on()` method for attaching event handlers. The older `.bind()` and `.delegate()` methods are being deprecated as of 3.0, but are still present. The API documentation explains how to rewrite the calls to the newer `.on()` method. + + +### Manipulation +#### Breaking change: `.wrapAll(function)` only calls the function once + +In previous versions, the `.wrapAll()` method acted like `.wrap()` when a function was passed. This has been corrected; now and `.wrapAll(function)` calls its function once, using the string result of the function call to wrap the entire collection. + +https://github.com/jquery/jquery/issues/1843 + + +### Offset + +#### Breaking change: Invalid input to the `.offset()` method + +When using the `.offset()` method, the first item in the jQuery collection must be a DOM element that has a DOM `getBoundingClientRect()` method. (All browsers supported by jQuery 3.0 have this API.) Any other input may result in jQuery throwing an error. Also note that the element must be visible and currently in a document (i.e., not disconnected). + +https://github.com/jquery/jquery/issues/2115 +https://github.com/jquery/jquery/issues/2114 + + +### Selector + +#### Breaking change: Behavior of `:hidden` and `:visible` + +An element is considered now visible if it has a layout box returned from the DOM `getClientRects()` method, even if that box has a height and/or width of zero. This means that elements such as `
` or an empty `` element that don't have height are considered to be visible. + +https://github.com/jquery/jquery/issues/2227 +https://github.com/jquery/jquery/issues/2604 + +#### Breaking change: `$("#")` and `$(document).find("#")` are invalid syntax + +jQuery 3.0 throws a syntax error if a selector string consists of nothing but a hash-mark. In previous versions, `$("#")` returned an empty collection and `$(document).find("#")` threw an error. + +https://github.com/jquery/jquery/pull/1682 + +#### Feature: New method `$.escapeSelector()` + +The new `$.escapeSelector( selector )` method takes a selector string and escapes any characters that would normally have special meaning in a CSS selector. It is essentially a shim for the [CSS Working Group's `CSS.escape()` method](https://drafts.csswg.org/cssom/#the-css.escape()-method) that runs on all of jQuery's supported browsers. This method is useful for situations where a class name or id name contains unusual characters. + +For example, if an element on the page has an id of "abc.def" it cannot be selected with `$( "#abc.def" )` because the selector is parsed as "an element with id 'abc' that also has a class 'def'. However, it *can* be selected with $( "#" + $.escapeSelector( "abc.def" ) )`. + + +https://github.com/jquery/jquery/issues/1761 + + + +#### Deprecated: `$.expr[":"]` and `$.expr.filters` + +These two names for defining custom selectors through jQuery's Sizzle selection engine are the same as `$.expr.pseudos`, so we are deprecating the redundant names. + +### Serialize + +#### Breaking change: $.param() no longer converts %20 to a plus sign + +In forms that are POST-ed via `$.ajax()`, the [specification](https://url.spec.whatwg.org/#concept-urlencoded-byte-serializer) for `application/x-www-form-urlencoded` encoding says that any occurrence of a space should be converted to the `+` character. Previously, jQuery implemented this by doing the conversion in `$.param()`. Now, that conversion has been moved into `$.ajax()`. Data encoded via `$.param()` will convert spaces to `%20`, which makes it directly compatible with the use of the native JavaScript `encodeURIComponent()` and `decodeURIComponent()` methods. + +https://github.com/jquery/jquery/issues/2658 + + + + + + + + + + From d43472651265fb9935c9722f7eb529d266b91f2b Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Fri, 22 Apr 2016 15:19:26 -0400 Subject: [PATCH 013/259] 2.1.20 --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 5387ecf..776d25e 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "jquery.com", "title": "jQuery Homepage", - "version": "2.1.19", + "version": "2.1.20", "homepage": "https://github.com/jquery/jquery.com", "author": { "name": "jQuery Foundation and other contributors" From eda612f0e963b55c41c4d96a10725048a8d2bc00 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Go=C5=82=C4=99biowski?= Date: Mon, 25 Apr 2016 20:01:42 +0200 Subject: [PATCH 014/259] Upgrade guide: drop Yandex.Browser mentions --- pages/upgrade-guide/3.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index e311f21..db3425e 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -17,7 +17,7 @@ As of jQuery 3.0, the following browsers are supported: * Internet Explorer: 9+ * Chrome, Edge, Firefox, Safari: Current and Current - 1 -* Opera and Yandex Browser: Current +* Opera: Current * Safari Mobile iOS: 7+ * Android: 2.3 (limited) * Android 4.0+ From 1ac70a367171f92f3c261f3b17058697ac8b5c13 Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Wed, 27 Apr 2016 16:16:34 -0400 Subject: [PATCH 015/259] Docs: Add section on Strict Mode for 3.0 upgrade guide --- pages/upgrade-guide/3.0.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index db3425e..4e4186c 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -123,6 +123,13 @@ https://github.com/jquery/jquery/issues/1990 ### Core +#### Breaking change: jQuery 3.0 runs in Strict Mode + +Now that all the browsers supported by jQuery 3.0 have `"use strict"`, jQuery is being built with this directive. Your code is not required to run in Strict Mode, so most existing code should not require any changes. The one case we encountered three years ago was that ASP.NET 4.0 used `arguments.caller.callee` to attempt tracing through call stacks in its `__doPostBack()` method. If you are still using a version of ASP.NET that still does this, keep using jQuery 2.x or earlier. Modern browsers support stack traces via `error.stack` so it should not ever be necessary to examine `arguments.caller.callee`. + +https://github.com/jquery/jquery/pull/3061 +https://bugs.jquery.com/ticket/13335 + #### Breaking change: document-ready handlers are now asynchronous The document-ready processing in jQuery has been powered by the `jQuery.Deferred` implementation since jQuery 1.6. As part of jQuery 3.0's alignment with the Promise/A+ standard, document-ready handlers are called asynchronously even if the document is currently ready at the point where the handler is added. This provides a consistent code execution order that is independent of whether the document is ready or not. For example, consider this code: From 9a42b81167467e2dbd6743f60e2f4ee30cad00f9 Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Wed, 27 Apr 2016 16:17:37 -0400 Subject: [PATCH 016/259] 2.1.21 --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 776d25e..95d0e72 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "jquery.com", "title": "jQuery Homepage", - "version": "2.1.20", + "version": "2.1.21", "homepage": "https://github.com/jquery/jquery.com", "author": { "name": "jQuery Foundation and other contributors" From 64c519fe77ffdeda2ec404ec3592ea2cead2ad85 Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Wed, 27 Apr 2016 16:27:32 -0400 Subject: [PATCH 017/259] Docs: Not every browser supports Strict Mode yet --- pages/upgrade-guide/3.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index 4e4186c..4345006 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -125,7 +125,7 @@ https://github.com/jquery/jquery/issues/1990 #### Breaking change: jQuery 3.0 runs in Strict Mode -Now that all the browsers supported by jQuery 3.0 have `"use strict"`, jQuery is being built with this directive. Your code is not required to run in Strict Mode, so most existing code should not require any changes. The one case we encountered three years ago was that ASP.NET 4.0 used `arguments.caller.callee` to attempt tracing through call stacks in its `__doPostBack()` method. If you are still using a version of ASP.NET that still does this, keep using jQuery 2.x or earlier. Modern browsers support stack traces via `error.stack` so it should not ever be necessary to examine `arguments.caller.callee`. +Now that most the browsers supported by jQuery 3.0 have `"use strict"`, jQuery is being built with this directive. Your code is not required to run in Strict Mode, so most existing code should not require any changes. The one case we encountered three years ago was that ASP.NET 4.0 used `arguments.caller.callee` to attempt tracing through call stacks in its `__doPostBack()` method. If you are still using a version of ASP.NET that still does this, keep using jQuery 2.x or earlier. Modern browsers support stack traces via `error.stack` so it should not ever be necessary to examine `arguments.caller.callee`. https://github.com/jquery/jquery/pull/3061 https://bugs.jquery.com/ticket/13335 From f5998b517bf462bb802eee077be1db95f2a49d15 Mon Sep 17 00:00:00 2001 From: Richard Gibson Date: Fri, 29 Apr 2016 00:28:23 -0400 Subject: [PATCH 018/259] Properly reference Promises/A+ --- pages/upgrade-guide/3.0.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index 4345006..b4c06da 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -63,7 +63,7 @@ For a complete and detailed list of all code changes, see the 3.0 milestone in t ### Ajax #### Breaking change: Special-case Deferred methods removed from $.ajax -The `jqXHR` object returned from `jQuery.ajax()` is a jQuery `Deferred` and has historically had three extra methods with names matching the arguments object of `success`, `error`, and `complete`. This often confused people who did not realize that the returned object should be treated like a `Deferred`. As of jQuery 3.0 these methods have been removed. As replacements, use the `Deferred` standard methods of `done`, `fail`, and `always`, or use the new `then` and `catch` methods for Promise/A+ compliance. +The `jqXHR` object returned from `jQuery.ajax()` is a jQuery `Deferred` and has historically had three extra methods with names matching the arguments object of `success`, `error`, and `complete`. This often confused people who did not realize that the returned object should be treated like a `Deferred`. As of jQuery 3.0 these methods have been removed. As replacements, use the `Deferred` standard methods of `done`, `fail`, and `always`, or use the new `then` and `catch` methods for Promises/A+ compliance. Note that this does not have any impact at all on the ajax callbacks of the same name passed through the `options` object, which continue to exist and are not deprecated. This only affects the jqXHR methods. @@ -132,7 +132,7 @@ https://bugs.jquery.com/ticket/13335 #### Breaking change: document-ready handlers are now asynchronous -The document-ready processing in jQuery has been powered by the `jQuery.Deferred` implementation since jQuery 1.6. As part of jQuery 3.0's alignment with the Promise/A+ standard, document-ready handlers are called asynchronously even if the document is currently ready at the point where the handler is added. This provides a consistent code execution order that is independent of whether the document is ready or not. For example, consider this code: +The document-ready processing in jQuery has been powered by the `jQuery.Deferred` implementation since jQuery 1.6. As part of jQuery 3.0's alignment with the Promises/A+ standard, document-ready handlers are called asynchronously even if the document is currently ready at the point where the handler is added. This provides a consistent code execution order that is independent of whether the document is ready or not. For example, consider this code: ```js $(function(){ @@ -273,16 +273,16 @@ https://github.com/jquery/jquery/issues/1751 ### Deferred -#### Breaking change and Feature: $.Deferred is now Promise/A+ compatible +#### Breaking change and Feature: $.Deferred is now Promises/A+ compatible -Deferreds have been updated for compatibility with Promise/A+ and ES2015 (a.k.a ES6) Promise. This introduces a `.catch()` method and makes some major changes to the `.then()` method. In particular, any exception thrown within a `.then()` callback now becomes a rejection value and we *strongly recommend* that you add a `.catch()` method to the end of your promise chain to avoid dificult debugging issues. +Deferreds have been updated for compatibility with Promises/A+ and ES2015 (a.k.a ES6) Promise. This introduces a `.catch()` method and makes some major changes to the `.then()` method. In particular, any exception thrown within a `.then()` callback now becomes a rejection value and we *strongly recommend* that you add a `.catch()` method to the end of your promise chain to avoid difficult debugging issues. The most likely place you may encounter this new behavior is when using the Deferreds that are produced by `jQuery.ajax()`, since the `jQXHR` object it returns is a superset of `$.Deferred`. -The Promise/A+ spec says that promises are always resolved with a single value and handlers are invoked without a `this` context, while `jQuery.ajax()` sometimes passes context and/or multiple values to its handlers. In most cases, though, the first argument is the most important of these values. If you are currently using a `.then()` you may only receive a single argument in your handler. To get context and/or more arguments, switch to the older `.done()` and `.fail()` methods which retain all the backward-compatible behavior: +The Promises/A+ spec says that promises are always resolved with a single value and handlers are invoked without a `this` context, while `jQuery.ajax()` sometimes passes context and/or multiple values to its handlers. In most cases, though, the first argument is the most important of these values. If you are currently using a `.then()` you may only receive a single argument in your handler. To get context and/or more arguments, switch to the older `.done()` and `.fail()` methods which retain all the backward-compatible behavior: ```js -// Typical old uses of .then() that are not Promise/A+ compatible +// Typical old uses of .then() that are not Promises/A+ compatible $.ajax("url").then( // success function( data, textStatus, jqXHR ) { /* code */ }, @@ -298,13 +298,13 @@ $.ajax("url") .fail(function( jqXHR, textStatus, errorThrown ) { /* code */ }); ``` -Another behavior change required for Promise/A+ compliance is that Deferred `.then()` callbacks are *always* called asynchronously. Previously, if a `.then()` callback was added to a Deferred that was already resolved or rejected, the callback would run immediately and synchronously. +Another behavior change required for Promises/A+ compliance is that Deferred `.then()` callbacks are *always* called asynchronously. Previously, if a `.then()` callback was added to a Deferred that was already resolved or rejected, the callback would run immediately and synchronously. -Deferred methods such as `.done()`, `.fail()`, and `.pipe()` retain their old behavior and so are not Promise/A+ compliant. If you require synchronous resolution, do not want exceptions converted to rejection values, or want thrown errors to bubble out of the function where they occur, you can use these methods instead of `.then()` and `.catch()`. +Deferred methods such as `.done()`, `.fail()`, and `.pipe()` retain their old behavior and so are not Promises/A+ compliant. If you require synchronous resolution, do not want exceptions converted to rejection values, or want thrown errors to bubble out of the function where they occur, you can use these methods instead of `.then()` and `.catch()`. In jQuery 1.x and 2.x, an uncaught exception inside a callback function halts code execution. The thrown exception bubbles up until it is caught inside a try/catch or reaches `window` and triggers `window.onerror`. -For example, consider this code using the new standard Promise/A behavior: +For example, consider this code using the new standard Promises/A+ behavior: ```js $.ajax("/status") @@ -343,7 +343,7 @@ https://github.com/jquery/jquery/issues/2736 The $.when() method now interprets that any input argument with a `.then()` method is a Promise or Deferred compatible object. In previous versions, if a single Deferred was passed as an input argument, `$.when()` would re-use it and return it as the output Deferred. Now, it *always* returns a new Deferred. This allows any type of`then`-able to be passed as input, including native ES6 Promise or Bluebird promises. You can also convert to the output Deferred to an ES6 promise with `Promise.resolve()` where native Promise is supported. -As of jQuery 3.0, the `$.when()` method no longer passes along progress notifications from input Deferreds to the output Deferred. Progress messages are not part of the Promise/A+ specification, and the behavior of progress notifications in `$.when()` were not previously documented in the jQuery API. +As of jQuery 3.0, the `$.when()` method no longer passes along progress notifications from input Deferreds to the output Deferred. Progress messages are not part of the Promises/A+ specification, and the behavior of progress notifications in `$.when()` were not previously documented in the jQuery API. https://github.com/jquery/jquery/issues/2710 https://github.com/jquery/jquery/issues/2546 @@ -379,9 +379,9 @@ Any code expecting hidden elements to be reshown with their previous _computed_ #### Feature: Animations now use requestAnimationFrame -On platforms that support the `requestAnimationFrame` API, which is pretty much everywhere but IE9, jQuery will now use that API when performing animations. This should result in animations that are smoother and use less CPU time � and save battery as well on mobile devices. +On platforms that support the `requestAnimationFrame` API, which is pretty much everywhere but IE9, jQuery will now use that API when performing animations. This should result in animations that are smoother and use less CPU time – and save battery as well on mobile devices. -jQuery tried using requestAnimationFrame a few years back but there were serious compatibility issues with existing code so we had to back it out. We think we�ve beaten most of those issues by suspending animations while a browser tab is out of view. Still, any code that depends on animations to always run in nearly real-time is making an unrealistic assumption. +jQuery tried using requestAnimationFrame a few years back but there were serious compatibility issues with existing code so we had to back it out. We think we’ve beaten most of those issues by suspending animations while a browser tab is out of view. Still, any code that depends on animations to always run in nearly real-time is making an unrealistic assumption. #### Deprecated: Additional easing function parameters From c878d3a114d04847f4d48ce009b119f6edf05d26 Mon Sep 17 00:00:00 2001 From: Richard Gibson Date: Fri, 29 Apr 2016 00:48:41 -0400 Subject: [PATCH 019/259] Docs: Fix non-ASCII characters Ref f5998b517bf462bb802eee077be1db95f2a49d15 --- pages/upgrade-guide/3.0.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index b4c06da..b959ecd 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -379,9 +379,9 @@ Any code expecting hidden elements to be reshown with their previous _computed_ #### Feature: Animations now use requestAnimationFrame -On platforms that support the `requestAnimationFrame` API, which is pretty much everywhere but IE9, jQuery will now use that API when performing animations. This should result in animations that are smoother and use less CPU time – and save battery as well on mobile devices. +On platforms that support the `requestAnimationFrame` API, which is pretty much everywhere but IE9, jQuery will now use that API when performing animations. This should result in animations that are smoother and use less CPU time—and save battery as well on mobile devices. -jQuery tried using requestAnimationFrame a few years back but there were serious compatibility issues with existing code so we had to back it out. We think we’ve beaten most of those issues by suspending animations while a browser tab is out of view. Still, any code that depends on animations to always run in nearly real-time is making an unrealistic assumption. +jQuery tried using requestAnimationFrame a few years back but there were serious compatibility issues with existing code so we had to back it out. We think we’ve beaten most of those issues by suspending animations while a browser tab is out of view. Still, any code that depends on animations to always run in nearly real-time is making an unrealistic assumption. #### Deprecated: Additional easing function parameters From 5a7e724ff49ec8621132a4bf048345988e0de93c Mon Sep 17 00:00:00 2001 From: Pritesh Gupta Date: Thu, 28 Apr 2016 18:57:15 -0700 Subject: [PATCH 020/259] Upgrade guide to 3.0: Missing "of" Closes gh-127 --- pages/upgrade-guide/3.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index b959ecd..8e75768 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -125,7 +125,7 @@ https://github.com/jquery/jquery/issues/1990 #### Breaking change: jQuery 3.0 runs in Strict Mode -Now that most the browsers supported by jQuery 3.0 have `"use strict"`, jQuery is being built with this directive. Your code is not required to run in Strict Mode, so most existing code should not require any changes. The one case we encountered three years ago was that ASP.NET 4.0 used `arguments.caller.callee` to attempt tracing through call stacks in its `__doPostBack()` method. If you are still using a version of ASP.NET that still does this, keep using jQuery 2.x or earlier. Modern browsers support stack traces via `error.stack` so it should not ever be necessary to examine `arguments.caller.callee`. +Now that most of the browsers supported by jQuery 3.0 have `"use strict"`, jQuery is being built with this directive. Your code is not required to run in Strict Mode, so most existing code should not require any changes. The one case we encountered three years ago was that ASP.NET 4.0 used `arguments.caller.callee` to attempt tracing through call stacks in its `__doPostBack()` method. If you are still using a version of ASP.NET that still does this, keep using jQuery 2.x or earlier. Modern browsers support stack traces via `error.stack` so it should not ever be necessary to examine `arguments.caller.callee`. https://github.com/jquery/jquery/pull/3061 https://bugs.jquery.com/ticket/13335 From 46394ea006c310ef436a7fdfce8a148c01fc9092 Mon Sep 17 00:00:00 2001 From: Richard Gibson Date: Fri, 29 Apr 2016 00:42:06 -0400 Subject: [PATCH 021/259] Docs: Describe Deferred default callback context changes Ref https://github.com/jquery/jquery/issues/3060 Closes gh-128 --- pages/upgrade-guide/3.0.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index 8e75768..a389f71 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -275,9 +275,17 @@ https://github.com/jquery/jquery/issues/1751 #### Breaking change and Feature: $.Deferred is now Promises/A+ compatible -Deferreds have been updated for compatibility with Promises/A+ and ES2015 (a.k.a ES6) Promise. This introduces a `.catch()` method and makes some major changes to the `.then()` method. In particular, any exception thrown within a `.then()` callback now becomes a rejection value and we *strongly recommend* that you add a `.catch()` method to the end of your promise chain to avoid difficult debugging issues. +Deferreds have been updated for compatibility with Promises/A+ and ES2015 (a.k.a ES6) Promise, a change with significant consequences. -The most likely place you may encounter this new behavior is when using the Deferreds that are produced by `jQuery.ajax()`, since the `jQXHR` object it returns is a superset of `$.Deferred`. +##### Resolution + +`.resolve`, `.reject`, and `.notify` now set `undefined` context instead of using the promise of the Deferred object with which they are associated. To set an explicit context, use `.resolveWith`, `.rejectWith`, and `.notifyWith`. + +https://github.com/jquery/jquery/issues/3060 + +##### Callbacks + +Major changes have been made to the `.then()` method. In particular, any exception thrown within a `.then()` callback now becomes a rejection value and we *strongly recommend* that you add a `.catch()` method (new in 3.0) to the end of your promise chain to avoid difficult debugging issues. The most likely place you may encounter this new behavior is when using the Deferreds that are produced by `jQuery.ajax()`, since the `jQXHR` object returned is a superset of `$.Deferred`. The Promises/A+ spec says that promises are always resolved with a single value and handlers are invoked without a `this` context, while `jQuery.ajax()` sometimes passes context and/or multiple values to its handlers. In most cases, though, the first argument is the most important of these values. If you are currently using a `.then()` you may only receive a single argument in your handler. To get context and/or more arguments, switch to the older `.done()` and `.fail()` methods which retain all the backward-compatible behavior: From e3a92899bf8b02afbc5ac39652ab9c9252ee8c4b Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Fri, 29 Apr 2016 17:32:20 -0400 Subject: [PATCH 022/259] Docs: Update description for .toggleClass() in 3.0 upgrade guide --- pages/upgrade-guide/3.0.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index a389f71..a70c095 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -109,9 +109,9 @@ SVG has never been fully supported by jQuery and this hasn't changed in jQuery 3 https://github.com/jquery/jquery/issues/2199 -#### Deprecated: `.toggleClass()` with no arguments +#### Deprecated: `.toggleClass()` with no arguments and `.toggleClass( Boolean )` -Although a signature for `.toggleClass()` with no arguments was previously documented, its actual behavior was never fully defined. This undefined behavior is now deprecated so it will not be documented. +Although a signature for these two cases was documented, its actual behavior was never fully defined. This undefined behavior is now deprecated so it will not be documented. You may find you were accidentally using the functionality because `.toggleClass( undefined )` behaves the same as a call with no arguments, even though it was invalid input. ### Callbacks From 53baf55d0ae4b106e77231c970fc850413c04928 Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Wed, 4 May 2016 16:54:53 -0400 Subject: [PATCH 023/259] Docs: Remove TODO in upgrade guide --- pages/upgrade-guide/3.0.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index a70c095..5298137 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -382,9 +382,6 @@ Further, while `.show()` and similar calls will continue to force visibility of Any code expecting hidden elements to be reshown with their previous _computed_ display styles, or disconnected elements to treated as hidden, should be reviewed. The team created a [table](https://docs.google.com/spreadsheets/d/1UaISjcS3UMxVJ7eSBIXtK-jqF8Grl67w640peCqlkoc/edit) of all the possibilities related to the display state and show/hide actions in order to minimize the setting of non-empty inline styles. -**SITUATIONS WHERE THE OUTCOME WILL BE DIFFERENT** -**WHAT USERS NEED TO DO TO FIX IT** - #### Feature: Animations now use requestAnimationFrame On platforms that support the `requestAnimationFrame` API, which is pretty much everywhere but IE9, jQuery will now use that API when performing animations. This should result in animations that are smoother and use less CPU time—and save battery as well on mobile devices. From c6ce58ed339fad216c03855976130cc8b6cb22f1 Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Wed, 4 May 2016 17:07:41 -0400 Subject: [PATCH 024/259] Docs: Add note about fixHooks removal --- pages/upgrade-guide/3.0.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index 5298137..2801714 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -422,6 +422,14 @@ jQuery no longer supports a synthetic event named `"ready"` that can be used wit https://github.com/jquery/jquery/issues/2264 +#### Breaking change: `jQuery.event.props` and `jQuery.event.fixHooks` removed + +jQuery's event handling performance got a major improvement with a reorganization of some of the low-level plumbing. The main improvement is that jQuery now only calculates or copies a property on the first access, rather than calculating and copying them up front. This is a really big win with properties that may force layout that the event handler may not even need. The most common use we know of was to add properties for pointer events, which is no longer necessary because those events are supported already in jQuery 3.0. The jQuery Migrate plugin provides support for these properties if you still need them. The team is interested in understanding other use cases before defining new APIs, so feel free to open a ticket. + +https://github.com/jquery/jquery/issues/3103 +https://github.com/jquery/jquery/issues/1746 +https://learn.jquery.com/events/event-extensions/ + #### Deprecated: .bind() and .delegate() Five years ago in jQuery 1.7 we introduced the `.on()` method for attaching event handlers. The older `.bind()` and `.delegate()` methods are being deprecated as of 3.0, but are still present. The API documentation explains how to rewrite the calls to the newer `.on()` method. From 0e19a9cc42fb202fc77471f89731561f8f4bf965 Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Fri, 6 May 2016 10:22:04 -0400 Subject: [PATCH 025/259] Docs: Add section on pageX/Y and tweak event props discussion. --- pages/upgrade-guide/3.0.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index 2801714..7ebe8f8 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -422,9 +422,15 @@ jQuery no longer supports a synthetic event named `"ready"` that can be used wit https://github.com/jquery/jquery/issues/2264 +#### Breaking change: `event.pageX` and `event.pageY` normalization removed + +All the browsers officially supported by jQuery 3.0 provide the pageX and pageY properties in their events, so the jQuery code to calculate these values from other event properties has been removed. This change should not affect mainstream browsers, but there may be obscure environments where these properties are not present. If you find one, please open a ticket. + +https://github.com/jquery/jquery/issues/3092 + #### Breaking change: `jQuery.event.props` and `jQuery.event.fixHooks` removed -jQuery's event handling performance got a major improvement with a reorganization of some of the low-level plumbing. The main improvement is that jQuery now only calculates or copies a property on the first access, rather than calculating and copying them up front. This is a really big win with properties that may force layout that the event handler may not even need. The most common use we know of was to add properties for pointer events, which is no longer necessary because those events are supported already in jQuery 3.0. The jQuery Migrate plugin provides support for these properties if you still need them. The team is interested in understanding other use cases before defining new APIs, so feel free to open a ticket. +jQuery's event handling performance increased thanks to a reorganization of event property management. The main improvement is that jQuery now only calculates or copies a property on the first access, rather than calculating and copying them up front. This is a really big win with properties that may force layout that the event handler may not even need. The most common use we know of was to add properties for pointer events, which is no longer necessary because those events are supported already in jQuery 3.0. The jQuery Migrate plugin provides support for these properties if you still need them. The related but undocumented `mouseHooks` and `keyHooks` lists were removed as well. The team is interested in understanding other use cases before defining new APIs, so feel free to open a ticket. https://github.com/jquery/jquery/issues/3103 https://github.com/jquery/jquery/issues/1746 From 7c654a59c74672114d102fe4775d103c09cc3f9a Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Fri, 6 May 2016 13:19:53 -0400 Subject: [PATCH 026/259] Docs: Add note on selectors throwing; mention .unbind and .undelegate --- pages/upgrade-guide/3.0.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index 7ebe8f8..b181a86 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -436,9 +436,15 @@ https://github.com/jquery/jquery/issues/3103 https://github.com/jquery/jquery/issues/1746 https://learn.jquery.com/events/event-extensions/ +#### Breaking change: Delegated events with bad selectors throw *immediately* + +Before jQuery 3.0, the selector used in a delegated event wasn't used until the first time that event occurred on the element. This sometimes led to hard-to-debug cases where the error was far removed from the time and code where the mistake was made. Now the selector is tested when the event is attached and throws an error if it is not valid. The only reason this is considered a breaking change is that code might use an invalid selector when attaching an event that never occurs, and that case previously would have never thrown an error. + +https://github.com/jquery/jquery/issues/3071 + #### Deprecated: .bind() and .delegate() -Five years ago in jQuery 1.7 we introduced the `.on()` method for attaching event handlers. The older `.bind()` and `.delegate()` methods are being deprecated as of 3.0, but are still present. The API documentation explains how to rewrite the calls to the newer `.on()` method. +Five years ago in jQuery 1.7 we introduced the `.on()` method for attaching event handlers. The older `.bind()`, `.unbind()`, `.delegate()` and `.undelegate()` methods are being deprecated as of 3.0, but are still present. The API documentation explains how to rewrite the calls using the `.on()` and `.off()` methods. ### Manipulation From 76efe3142a8824f69117ad88abccf344a1306c67 Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Fri, 6 May 2016 13:20:51 -0400 Subject: [PATCH 027/259] 2.1.22 --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 95d0e72..3a327b3 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "jquery.com", "title": "jQuery Homepage", - "version": "2.1.21", + "version": "2.1.22", "homepage": "https://github.com/jquery/jquery.com", "author": { "name": "jQuery Foundation and other contributors" From 65b4f393b512335c8cf2f599ec711aa570305fbd Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Mon, 9 May 2016 12:33:06 -0400 Subject: [PATCH 028/259] Docs: Remove Android 2.3 support in 3.0 upgrade guide --- pages/upgrade-guide/3.0.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index b181a86..cea1fb4 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -19,11 +19,8 @@ As of jQuery 3.0, the following browsers are supported: * Chrome, Edge, Firefox, Safari: Current and Current - 1 * Opera: Current * Safari Mobile iOS: 7+ -* Android: 2.3 (limited) * Android 4.0+ -The limited Android 2.3 support may not correct minor known issues with positioning, but jQuery should not throw exceptions in Android 2.3 on valid API inputs. - jQuery team policy is to only change browser support on major-version updates, so this list will apply until at least jQuery 4 arrives. ## jQuery Migrate Plugin From cad8d41225be9ff4564efbb1124bc5a8cdd7a643 Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Mon, 9 May 2016 12:33:52 -0400 Subject: [PATCH 029/259] 2.1.23 --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 3a327b3..7b61053 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "jquery.com", "title": "jQuery Homepage", - "version": "2.1.22", + "version": "2.1.23", "homepage": "https://github.com/jquery/jquery.com", "author": { "name": "jQuery Foundation and other contributors" From 837805da89dbdc85e26f5c59836aec03a8b0c667 Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Mon, 9 May 2016 15:26:47 -0400 Subject: [PATCH 030/259] Docs: Be consistent about `jQuery` vs `$` in upgrade guide Fixes #130 --- pages/upgrade-guide/3.0.md | 58 +++++++++++++++++++------------------- 1 file changed, 29 insertions(+), 29 deletions(-) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index cea1fb4..f1a9ef5 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -59,7 +59,7 @@ Remember that the jQuery Migrate plugin described above can detect and warn abou For a complete and detailed list of all code changes, see the 3.0 milestone in the [jQuery Core issue tracker](https://github.com/jquery/jquery/issues?q=is%3Aopen+is%3Aissue+milestone%3A3.0.0) or the [version diff](https://github.com/jquery/jquery/compare/2.2-stable...master). ### Ajax -#### Breaking change: Special-case Deferred methods removed from $.ajax +#### Breaking change: Special-case Deferred methods removed from jQuery.ajax The `jqXHR` object returned from `jQuery.ajax()` is a jQuery `Deferred` and has historically had three extra methods with names matching the arguments object of `success`, `error`, and `complete`. This often confused people who did not realize that the returned object should be treated like a `Deferred`. As of jQuery 3.0 these methods have been removed. As replacements, use the `Deferred` standard methods of `done`, `fail`, and `always`, or use the new `then` and `catch` methods for Promises/A+ compliance. Note that this does not have any impact at all on the ajax callbacks of the same name passed through the `options` object, which continue to exist and are not deprecated. This only affects the jqXHR methods. @@ -68,17 +68,17 @@ https://github.com/jquery/jquery/issues/2084 #### Breaking change: Cross-domain script requests must be declared -When making a request via `$.ajax()` or `$.get()` for a script on a domain other than the one that hosts the document, you must now explicitly specify `dataType: "script"` in the options. This prevents the possibility of an attack where the remote site delivers non-script content but later decides to serve a script that has malicious intent. Since `$.getScript()` explicitly sets `dataType: "script"` it is unaffected by this change. +When making a request via `jQuery.ajax()` or `jQuery.get()` for a script on a domain other than the one that hosts the document, you must now explicitly specify `dataType: "script"` in the options. This prevents the possibility of an attack where the remote site delivers non-script content but later decides to serve a script that has malicious intent. Since `jQuery.getScript()` explicitly sets `dataType: "script"` it is unaffected by this change. -#### Breaking change: Hash in a URL is preserved in a `$.ajax()` call +#### Breaking change: Hash in a URL is preserved in a `jQuery.ajax()` call -The `$.ajax()` method no longer strips off the hash in the URL if it is provided, and sends the full URL to the transport (xhr, script, jsonp, or custom transport). If the server at the other end of the connection cannot deal with a hash on a URL, strip it off before sending the request. +The `jQuery.ajax()` method no longer strips off the hash in the URL if it is provided, and sends the full URL to the transport (xhr, script, jsonp, or custom transport). If the server at the other end of the connection cannot deal with a hash on a URL, strip it off before sending the request. https://github.com/jquery/jquery/issues/1732 -#### Feature: New signature for $.get() AND $.post() +#### Feature: New signature for jQuery.get() AND jQuery.post() -jQuery 3 adds a new signature for the `$.get()` and the `$.post()` functions by adding a `settings` parameter. It's an object that can possess many properties and its the same object that you can provide to [`$.ajax()`](http://api.jquery.com/jquery.ajax/#jQuery-ajax-settings). +jQuery 3 adds a new signature for the `jQuery.get()` and the `jQuery.post()` functions by adding a `settings` parameter. It's an object that can possess many properties and its the same object that you can provide to [`jQuery.ajax()`](http://api.jquery.com/jquery.ajax/#jQuery-ajax-settings). https://github.com/jquery/jquery/issues/1986 @@ -142,14 +142,14 @@ In jQuery 3.0 this will always log "outside ready" followed by "ready" regardles Since handlers now execute independently of each other, an exception or failure in one document-ready handler no longer prevents other document-ready handlers from running. -In custom builds where the `deferred` module is excluded, an alternative implementation of the document-ready code is used. This implementation supports the `$.ready` promise but is not a `$.Deferred` object so it should only be used through `$.when()`. +In custom builds where the `deferred` module is excluded, an alternative implementation of the document-ready code is used. This implementation supports the `jQuery.ready` promise but is not a `jQuery.Deferred` object so it should only be used through `jQuery.when()`. https://github.com/jquery/jquery/issues/1823 https://github.com/jquery/jquery/pull/2891 -#### Breaking change: $.isNumeric() and custom `.toString()` +#### Breaking change: jQuery.isNumeric() and custom `.toString()` -The `$.isNumeric()` method is intended to be used with primitive numbers and strings that can be coerced to finite numbers. In particular, it no longer tries to obtain numbers from objects that have a `.toString()` method. Users needing specialized checks for other numerics should create their own validation functions. +The `jQuery.isNumeric()` method is intended to be used with primitive numbers and strings that can be coerced to finite numbers. In particular, it no longer tries to obtain numbers from objects that have a `.toString()` method. Users needing specialized checks for other numerics should create their own validation functions. https://github.com/jquery/jquery/issues/2662 @@ -201,9 +201,9 @@ for ( let elem of elems ) { ``` https://github.com/jquery/jquery/issues/1693 -#### Feature: `$.ready` promise is formally supported +#### Feature: `jQuery.ready` promise is formally supported -`$.ready` has been consumable as a promise-like object ("thenable" in Promise terms) since jQuery version 1.8. As of jQuery 3.0 this object is documented as supported via `$.when` or the native `Promise.resolve()`. No code should make assumptions about whether this object is a jQuery `Deferred` or some other type of promise object such as a native Promise. Typical usage might look like this: +`jQuery.ready` has been consumable as a promise-like object ("thenable" in Promise terms) since jQuery version 1.8. As of jQuery 3.0 this object is documented as supported via `jQuery.when` or the native `Promise.resolve()`. No code should make assumptions about whether this object is a jQuery `Deferred` or some other type of promise object such as a native Promise. Typical usage might look like this: ```js $.when( $.ready, $.getScript("optional.js") ).then(function() { @@ -215,18 +215,18 @@ $.when( $.ready, $.getScript("optional.js") ).then(function() { https://github.com/jquery/api.jquery.com/pull/530 -#### Deprecated: `$.unique()`, renamed to `$.uniqueSort()` +#### Deprecated: `jQuery.unique()`, renamed to `jQuery.uniqueSort()` -The `$.unique()` method has been renamed to `$.uniqueSort()` to make its behavior easier to understand. There is no change to functionality here, only a rename. +The `jQuery.unique()` method has been renamed to `jQuery.uniqueSort()` to make its behavior easier to understand. There is no change to functionality here, only a rename. -#### Deprecated: `$.parseJSON()` +#### Deprecated: `jQuery.parseJSON()` -Since all the browsers supported by jQuery 3.0 support the native `JSON.parse()` method, we are deprecating `$.parseJSON()`. +Since all the browsers supported by jQuery 3.0 support the native `JSON.parse()` method, we are deprecating `jQuery.parseJSON()`. https://github.com/jquery/jquery/issues/2800 -#### Deprecated: document-ready handlers other than `$(function)` +#### Deprecated: document-ready handlers other than `jQuery(function)` Due to historical compatibility issues there are a multitude of ways to set a document ready handler. All of the following are equivalent and call the function `fn` when the document is ready: @@ -270,7 +270,7 @@ https://github.com/jquery/jquery/issues/1751 ### Deferred -#### Breaking change and Feature: $.Deferred is now Promises/A+ compatible +#### Breaking change and Feature: jQuery.Deferred is now Promises/A+ compatible Deferreds have been updated for compatibility with Promises/A+ and ES2015 (a.k.a ES6) Promise, a change with significant consequences. @@ -282,7 +282,7 @@ https://github.com/jquery/jquery/issues/3060 ##### Callbacks -Major changes have been made to the `.then()` method. In particular, any exception thrown within a `.then()` callback now becomes a rejection value and we *strongly recommend* that you add a `.catch()` method (new in 3.0) to the end of your promise chain to avoid difficult debugging issues. The most likely place you may encounter this new behavior is when using the Deferreds that are produced by `jQuery.ajax()`, since the `jQXHR` object returned is a superset of `$.Deferred`. +Major changes have been made to the `.then()` method. In particular, any exception thrown within a `.then()` callback now becomes a rejection value and we *strongly recommend* that you add a `.catch()` method (new in 3.0) to the end of your promise chain to avoid difficult debugging issues. The most likely place you may encounter this new behavior is when using the Deferreds that are produced by `jQuery.ajax()`, since the `jQXHR` object returned is a superset of `jQuery.Deferred`. The Promises/A+ spec says that promises are always resolved with a single value and handlers are invoked without a `this` context, while `jQuery.ajax()` sometimes passes context and/or multiple values to its handlers. In most cases, though, the first argument is the most important of these values. If you are currently using a `.then()` you may only receive a single argument in your handler. To get context and/or more arguments, switch to the older `.done()` and `.fail()` methods which retain all the backward-compatible behavior: @@ -344,11 +344,11 @@ https://github.com/jquery/jquery/issues/1722 https://github.com/jquery/jquery/issues/2102 https://github.com/jquery/jquery/issues/2736 -#### Breaking change and Feature: $.when() inputs and progress notifications +#### Breaking change and Feature: jQuery.when() inputs and progress notifications -The $.when() method now interprets that any input argument with a `.then()` method is a Promise or Deferred compatible object. In previous versions, if a single Deferred was passed as an input argument, `$.when()` would re-use it and return it as the output Deferred. Now, it *always* returns a new Deferred. This allows any type of`then`-able to be passed as input, including native ES6 Promise or Bluebird promises. You can also convert to the output Deferred to an ES6 promise with `Promise.resolve()` where native Promise is supported. +The jQuery.when() method now interprets that any input argument with a `.then()` method is a Promise or Deferred compatible object. In previous versions, if a single Deferred was passed as an input argument, `jQuery.when()` would re-use it and return it as the output Deferred. Now, it *always* returns a new Deferred. This allows any type of`then`-able to be passed as input, including native ES6 Promise or Bluebird promises. You can also convert to the output Deferred to an ES6 promise with `Promise.resolve()` where native Promise is supported. -As of jQuery 3.0, the `$.when()` method no longer passes along progress notifications from input Deferreds to the output Deferred. Progress messages are not part of the Promises/A+ specification, and the behavior of progress notifications in `$.when()` were not previously documented in the jQuery API. +As of jQuery 3.0, the `jQuery.when()` method no longer passes along progress notifications from input Deferreds to the output Deferred. Progress messages are not part of the Promises/A+ specification, and the behavior of progress notifications in `jQuery.when()` were not previously documented in the jQuery API. https://github.com/jquery/jquery/issues/2710 https://github.com/jquery/jquery/issues/2546 @@ -471,15 +471,15 @@ An element is considered now visible if it has a layout box returned from the DO https://github.com/jquery/jquery/issues/2227 https://github.com/jquery/jquery/issues/2604 -#### Breaking change: `$("#")` and `$(document).find("#")` are invalid syntax +#### Breaking change: `jQuery("#")` and `.find("#")` are invalid syntax -jQuery 3.0 throws a syntax error if a selector string consists of nothing but a hash-mark. In previous versions, `$("#")` returned an empty collection and `$(document).find("#")` threw an error. +jQuery 3.0 throws a syntax error if a selector string consists of nothing but a hash-mark. In previous versions, `$("#")` returned an empty collection and `.find("#")` threw an error. https://github.com/jquery/jquery/pull/1682 -#### Feature: New method `$.escapeSelector()` +#### Feature: New method `jQuery.escapeSelector()` -The new `$.escapeSelector( selector )` method takes a selector string and escapes any characters that would normally have special meaning in a CSS selector. It is essentially a shim for the [CSS Working Group's `CSS.escape()` method](https://drafts.csswg.org/cssom/#the-css.escape()-method) that runs on all of jQuery's supported browsers. This method is useful for situations where a class name or id name contains unusual characters. +The new `jQuery.escapeSelector( selector )` method takes a selector string and escapes any characters that would normally have special meaning in a CSS selector. It is essentially a shim for the [CSS Working Group's `CSS.escape()` method](https://drafts.csswg.org/cssom/#the-css.escape()-method) that runs on all of jQuery's supported browsers. This method is useful for situations where a class name or id name contains unusual characters. For example, if an element on the page has an id of "abc.def" it cannot be selected with `$( "#abc.def" )` because the selector is parsed as "an element with id 'abc' that also has a class 'def'. However, it *can* be selected with $( "#" + $.escapeSelector( "abc.def" ) )`. @@ -488,15 +488,15 @@ https://github.com/jquery/jquery/issues/1761 -#### Deprecated: `$.expr[":"]` and `$.expr.filters` +#### Deprecated: `jQuery.expr[":"]` and `jQuery.expr.filters` -These two names for defining custom selectors through jQuery's Sizzle selection engine are the same as `$.expr.pseudos`, so we are deprecating the redundant names. +These two names for defining custom selectors through jQuery's Sizzle selection engine are the same as `jQuery.expr.pseudos`, so we are deprecating the redundant names. ### Serialize -#### Breaking change: $.param() no longer converts %20 to a plus sign +#### Breaking change: jQuery.param() no longer converts %20 to a plus sign -In forms that are POST-ed via `$.ajax()`, the [specification](https://url.spec.whatwg.org/#concept-urlencoded-byte-serializer) for `application/x-www-form-urlencoded` encoding says that any occurrence of a space should be converted to the `+` character. Previously, jQuery implemented this by doing the conversion in `$.param()`. Now, that conversion has been moved into `$.ajax()`. Data encoded via `$.param()` will convert spaces to `%20`, which makes it directly compatible with the use of the native JavaScript `encodeURIComponent()` and `decodeURIComponent()` methods. +In forms that are POST-ed via `jQuery.ajax()`, the [specification](https://url.spec.whatwg.org/#concept-urlencoded-byte-serializer) for `application/x-www-form-urlencoded` encoding says that any occurrence of a space should be converted to the `+` character. Previously, jQuery implemented this by doing the conversion in `jQuery.param()`. Now, that conversion has been moved into `jQuery.ajax()`. Data encoded via `jQuery.param()` will convert spaces to `%20`, which makes it directly compatible with the use of the native JavaScript `encodeURIComponent()` and `decodeURIComponent()` methods. https://github.com/jquery/jquery/issues/2658 From a63a79a1d6ac27e491d133d477a77b91f5f43197 Mon Sep 17 00:00:00 2001 From: Richard Gibson Date: Mon, 16 May 2016 12:23:42 -0400 Subject: [PATCH 031/259] Docs: Document Deferred rejection callback return value handling Also cleans up the Deferred section a little. Closes gh-131 --- pages/upgrade-guide/3.0.md | 59 +++++++++++++++++++++----------------- 1 file changed, 32 insertions(+), 27 deletions(-) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index f1a9ef5..15a5ce3 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -274,38 +274,18 @@ https://github.com/jquery/jquery/issues/1751 Deferreds have been updated for compatibility with Promises/A+ and ES2015 (a.k.a ES6) Promise, a change with significant consequences. +https://github.com/jquery/jquery/issues/1722 +https://github.com/jquery/jquery/issues/2102 + ##### Resolution `.resolve`, `.reject`, and `.notify` now set `undefined` context instead of using the promise of the Deferred object with which they are associated. To set an explicit context, use `.resolveWith`, `.rejectWith`, and `.notifyWith`. https://github.com/jquery/jquery/issues/3060 -##### Callbacks - -Major changes have been made to the `.then()` method. In particular, any exception thrown within a `.then()` callback now becomes a rejection value and we *strongly recommend* that you add a `.catch()` method (new in 3.0) to the end of your promise chain to avoid difficult debugging issues. The most likely place you may encounter this new behavior is when using the Deferreds that are produced by `jQuery.ajax()`, since the `jQXHR` object returned is a superset of `jQuery.Deferred`. +##### Callback exit -The Promises/A+ spec says that promises are always resolved with a single value and handlers are invoked without a `this` context, while `jQuery.ajax()` sometimes passes context and/or multiple values to its handlers. In most cases, though, the first argument is the most important of these values. If you are currently using a `.then()` you may only receive a single argument in your handler. To get context and/or more arguments, switch to the older `.done()` and `.fail()` methods which retain all the backward-compatible behavior: - -```js -// Typical old uses of .then() that are not Promises/A+ compatible -$.ajax("url").then( - // success - function( data, textStatus, jqXHR ) { /* code */ }, - // error - function( jqXHR, textStatus, errorThrown ) { /* code */ } -); - -// Rewrite to this in order to maintain previous behavior -$.ajax("url") - // success - .done(function( data, textStatus, jqXHR ) { /* code */ }) - // error - .fail(function( jqXHR, textStatus, errorThrown ) { /* code */ }); -``` - -Another behavior change required for Promises/A+ compliance is that Deferred `.then()` callbacks are *always* called asynchronously. Previously, if a `.then()` callback was added to a Deferred that was already resolved or rejected, the callback would run immediately and synchronously. - -Deferred methods such as `.done()`, `.fail()`, and `.pipe()` retain their old behavior and so are not Promises/A+ compliant. If you require synchronous resolution, do not want exceptions converted to rejection values, or want thrown errors to bubble out of the function where they occur, you can use these methods instead of `.then()` and `.catch()`. +Major changes have been made to the `.then()` method. In particular, any exception thrown within a `.then()` callback is now caught and converted into a rejection value, and any non-thenable value returned from a _rejection_ handler becomes a fulfillment value. We **strongly recommend** that you add a `.catch()` method (new in 3.0) to the end of your promise chain to avoid difficult debugging issues. The most likely place you may encounter this new behavior is when using the Deferreds that are produced by `jQuery.ajax()`, since the `jQXHR` object returned is a superset of `jQuery.Deferred`. In jQuery 1.x and 2.x, an uncaught exception inside a callback function halts code execution. The thrown exception bubbles up until it is caught inside a try/catch or reaches `window` and triggers `window.onerror`. @@ -340,10 +320,35 @@ $.ajax("/status") Note that jQuery logs a message to the console when it is inside a Deferred and a JavaScript exception occurs. These messages take the form `jQuery.Deferred exception: (error message)`. If you do not want any console output on these exceptions, set `jQuery.Deferred.exceptionHook` to `undefined`. If you need further help in finding errors reported this way, use the [jquery-deferred-reporter plugin](https://github.com/dmethvin/jquery-deferred-reporter) during development to obtain stack traces. -https://github.com/jquery/jquery/issues/1722 -https://github.com/jquery/jquery/issues/2102 https://github.com/jquery/jquery/issues/2736 +##### Callback invocation + +The Promises/A+ spec says that promises are always resolved with a single value and handlers are invoked without a `this` context, while jQuery Deferreds sometimes pass context and/or multiple values to their handlers. In most cases, though, the first argument is the most important of these values. If you are currently using `.then()`, you may only receive a single argument in your handler. To get context and/or more arguments, switch to the older `.done()` and `.fail()` methods which retain all the backward-compatible behavior: + +```js +// Typical old uses of .then() that are not Promises/A+ compatible +$.ajax("url").then( + // success + function( data, textStatus, jqXHR ) { /* code */ }, + // error + function( jqXHR, textStatus, errorThrown ) { /* code */ } +); + +// Rewrite to this in order to maintain previous behavior +$.ajax("url") + // success + .done(function( data, textStatus, jqXHR ) { /* code */ }) + // error + .fail(function( jqXHR, textStatus, errorThrown ) { /* code */ }); +``` + +Another behavior change required for Promises/A+ compliance is that Deferred `.then()` callbacks are *always* called asynchronously. Previously, if a `.then()` callback was added to a Deferred that was already resolved or rejected, the callback would run immediately and synchronously. + +##### Backwards compatibility + +Deferred methods such as `.done()`, `.fail()`, and `.pipe()` retain their old behavior and so are not Promises/A+ compliant. If you require synchronous resolution, do not want exceptions converted to rejection values or rejection callback returns converted to fulfillment values, or want thrown errors to bubble out of the function where they occur, you can use these methods instead of `.then()` and `.catch()`. + #### Breaking change and Feature: jQuery.when() inputs and progress notifications The jQuery.when() method now interprets that any input argument with a `.then()` method is a Promise or Deferred compatible object. In previous versions, if a single Deferred was passed as an input argument, `jQuery.when()` would re-use it and return it as the output Deferred. Now, it *always* returns a new Deferred. This allows any type of`then`-able to be passed as input, including native ES6 Promise or Bluebird promises. You can also convert to the output Deferred to an ES6 promise with `Promise.resolve()` where native Promise is supported. From a7e19f768c4bf2485c500a7571c844f85ba74d7a Mon Sep 17 00:00:00 2001 From: Richard Gibson Date: Thu, 5 May 2016 16:28:11 -0400 Subject: [PATCH 032/259] Docs: Describe jQuery.when split paths Ref https://github.com/jquery/jquery/commit/356a3bccb0e7468a2c8ce7d8c9c6cd0c5d436b8b Closes gh-129 --- pages/upgrade-guide/3.0.md | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index 15a5ce3..727d950 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -349,14 +349,24 @@ Another behavior change required for Promises/A+ compliance is that Deferred `.t Deferred methods such as `.done()`, `.fail()`, and `.pipe()` retain their old behavior and so are not Promises/A+ compliant. If you require synchronous resolution, do not want exceptions converted to rejection values or rejection callback returns converted to fulfillment values, or want thrown errors to bubble out of the function where they occur, you can use these methods instead of `.then()` and `.catch()`. -#### Breaking change and Feature: jQuery.when() inputs and progress notifications +#### Breaking change and Feature: jQuery.when() arguments -The jQuery.when() method now interprets that any input argument with a `.then()` method is a Promise or Deferred compatible object. In previous versions, if a single Deferred was passed as an input argument, `jQuery.when()` would re-use it and return it as the output Deferred. Now, it *always* returns a new Deferred. This allows any type of`then`-able to be passed as input, including native ES6 Promise or Bluebird promises. You can also convert to the output Deferred to an ES6 promise with `Promise.resolve()` where native Promise is supported. +`jQuery.when` now interprets any input argument with a `then` method as a Promise-compatible "[thenable](https://promisesaplus.com/#point-7)". This allows a much broader range of inputs, including native ES6 Promises and Bluebird promises. + +Further, a more clear distinction is now recognized between multi-argument calls to `jQuery.when` and single- or no-argument calls. +Multi-argument calls behave similarly to `Promise.all`, aggregating fulfillment values into a fulfillment array (with jQuery-specific enhancements of also aggregating fulfillment contexts and supporting multi-valued fulfillments), or alternatively rejecting with the first rejection value. +Single- and no-argument calls behave similarly to `Promise.resolve`, returning a Deferred that resolves identically to thenable or Promise-like input, or fulfills with its non-Promise input (as appropriate). +As of jQuery 3.0, both of these return a new Deferred (previous versions did not create a new Deferred when called with a single Deferred input). + +https://github.com/jquery/jquery/issues/2018 +https://github.com/jquery/jquery/issues/2546 +https://github.com/jquery/jquery/issues/3029 + +#### Breaking change: jQuery.when() progress notifications As of jQuery 3.0, the `jQuery.when()` method no longer passes along progress notifications from input Deferreds to the output Deferred. Progress messages are not part of the Promises/A+ specification, and the behavior of progress notifications in `jQuery.when()` were not previously documented in the jQuery API. https://github.com/jquery/jquery/issues/2710 -https://github.com/jquery/jquery/issues/2546 ### Dimensions From ab8ee5aef9ce38230397704b5a3571ebacea4aac Mon Sep 17 00:00:00 2001 From: Timmy Willison Date: Fri, 20 May 2016 13:43:07 -0400 Subject: [PATCH 033/259] Update to jQuery 1.12.4 and 2.2.4 --- pages/download.md | 22 +++++++++++----------- pages/index.html | 2 +- 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/pages/download.md b/pages/download.md index fc5d7fd..9864e87 100644 --- a/pages/download.md +++ b/pages/download.md @@ -23,14 +23,14 @@ Read the [jQuery 1.9 Upgrade Guide](https://jquery.com/upgrade-guide/1.9/) and the [jQuery 1.9 release blog post](https://blog.jquery.com/2013/01/15/jquery-1-9-final-jquery-2-0-beta-migrate-final-released/) for more information. -Download the compressed, production jQuery 1.12.3 +Download the compressed, production jQuery 1.12.4 -Download the uncompressed, development jQuery 1.12.3 +Download the uncompressed, development jQuery 1.12.4 -Download the map file for jQuery 1.12.3 +Download the map file for jQuery 1.12.4 -[jQuery 1.12.3 release -notes](https://blog.jquery.com/2016/04/05/jquery-1-11-3-and-2-2-3-released/) +[jQuery 1.12.4 release +notes](https://blog.jquery.com/2016/05/20/jquery-1-12-4-and-2-2-4-released/) ### jQuery 2.x @@ -40,14 +40,14 @@ Since IE 8 is still relatively common, we recommend using the 1.x version unless are certain no IE 6/7/8 users are visiting the site. Please read the [2.0 release notes](https://blog.jquery.com/2013/04/18/jquery-2-0-released/) carefully. -Download the compressed, production jQuery 2.2.3 +Download the compressed, production jQuery 2.2.4 -Download the uncompressed, development jQuery 2.2.3 +Download the uncompressed, development jQuery 2.2.4 -Download the map file for jQuery 2.2.3 +Download the map file for jQuery 2.2.4 -[jQuery 2.2.3 release -notes](https://blog.jquery.com/2016/04/05/jquery-1-11-3-and-2-2-3-released/) +[jQuery 2.2.4 release +notes](https://blog.jquery.com/2016/05/20/jquery-1-12-4-and-2-2-4-released/) ## Downloading jQuery using Bower jQuery is registered as a package with [Bower](http://bower.io). You can install the latest version of jQuery with the command: @@ -58,7 +58,7 @@ This will install jQuery to Bower's install directory, the default being `bower_ The jQuery Bower package contains additional files besides the default distribution. In most cases you can ignore these files, however if you wish to download the default release on its own you can use Bower to install jQuery from one of the above urls instead of the registered package. For example, if you wish to install just the compressed jQuery file, you can install just that file with the following command: ``` -bower install https://code.jquery.com/jquery-2.2.3.min.js +bower install https://code.jquery.com/jquery-2.2.4.min.js ``` ## jQuery Migrate Plugin diff --git a/pages/index.html b/pages/index.html index 000a9ea..5656bf5 100644 --- a/pages/index.html +++ b/pages/index.html @@ -12,7 +12,7 @@ Download jQuery - v1.12.3 or v2.2.3 + v1.12.4 or v2.2.4

View Source on GitHub → From 187764d6bd62c766d9f46c056bd964084e04132b Mon Sep 17 00:00:00 2001 From: Timmy Willison Date: Fri, 20 May 2016 13:45:39 -0400 Subject: [PATCH 034/259] 2.1.24 --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 7b61053..7494af7 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "jquery.com", "title": "jQuery Homepage", - "version": "2.1.23", + "version": "2.1.24", "homepage": "https://github.com/jquery/jquery.com", "author": { "name": "jQuery Foundation and other contributors" From 47b8e2b66a77e0617dde2c2675fe270d62f9fdee Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Go=C5=82=C4=99biowski?= Date: Sat, 21 May 2016 19:09:04 +0200 Subject: [PATCH 035/259] Docs: fix a typo Thanks @zowers for the report! --- pages/upgrade-guide/3.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index 727d950..0677f84 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -424,7 +424,7 @@ https://github.com/jquery/api.jquery.com/issues/912 #### Breaking change: .load(), .unload(), and .error() removed -These methods are shortcuts for event operations, but had several API limitations. The event `.load()` method conflicted with the ajax `.load()` method. The `.error()` method could not be used with `window.onerror` because of the way the DOM method is defined. If you need to attach errors by these names, use the `.on()` method, e.g. change `$("img").load(fn)` to `$(img).on("load", fn)`. +These methods are shortcuts for event operations, but had several API limitations. The event `.load()` method conflicted with the ajax `.load()` method. The `.error()` method could not be used with `window.onerror` because of the way the DOM method is defined. If you need to attach events by these names, use the `.on()` method, e.g. change `$("img").load(fn)` to `$(img).on("load", fn)`. https://github.com/jquery/jquery/issues/2286 From 00d89bd63b2951adbe557c416b1e8283839ae30b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Go=C5=82=C4=99biowski?= Date: Sat, 21 May 2016 19:09:16 +0200 Subject: [PATCH 036/259] 2.1.25 --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 7494af7..89d00e8 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "jquery.com", "title": "jQuery Homepage", - "version": "2.1.24", + "version": "2.1.25", "homepage": "https://github.com/jquery/jquery.com", "author": { "name": "jQuery Foundation and other contributors" From 262a32ff3b294a8538dd3e13bc31b30e8f81e2d1 Mon Sep 17 00:00:00 2001 From: Aurelio De Rosa Date: Wed, 1 Jun 2016 01:16:28 +0100 Subject: [PATCH 037/259] Upgrade guide 3.0: Minor improvements to jQuery.escapeSelector() Closes gh-133 --- pages/upgrade-guide/3.0.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/upgrade-guide/3.0.md b/pages/upgrade-guide/3.0.md index 0677f84..987d7bc 100644 --- a/pages/upgrade-guide/3.0.md +++ b/pages/upgrade-guide/3.0.md @@ -494,9 +494,9 @@ https://github.com/jquery/jquery/pull/1682 #### Feature: New method `jQuery.escapeSelector()` -The new `jQuery.escapeSelector( selector )` method takes a selector string and escapes any characters that would normally have special meaning in a CSS selector. It is essentially a shim for the [CSS Working Group's `CSS.escape()` method](https://drafts.csswg.org/cssom/#the-css.escape()-method) that runs on all of jQuery's supported browsers. This method is useful for situations where a class name or id name contains unusual characters. +The new `jQuery.escapeSelector( selector )` method takes a selector string and escapes any character that has a special meaning in a CSS selector. It is essentially a shim for the [CSS Working Group's `CSS.escape()` method](https://drafts.csswg.org/cssom/#the-css.escape%28%29-method) that runs on all of jQuery's supported browsers. This method is useful for situations where a class name or an ID contains characters that have a special meaning in CSS, such as the dot or the semicolon. -For example, if an element on the page has an id of "abc.def" it cannot be selected with `$( "#abc.def" )` because the selector is parsed as "an element with id 'abc' that also has a class 'def'. However, it *can* be selected with $( "#" + $.escapeSelector( "abc.def" ) )`. +For example, if an element on the page has an id of "abc.def" it cannot be selected with `$( "#abc.def" )` because the selector is parsed as "an element with id 'abc' that also has a class 'def'. However, it *can* be selected with `$( "#" + $.escapeSelector( "abc.def" ) )`. https://github.com/jquery/jquery/issues/1761 From f04b4c9bced4530fed570de063de260112d93997 Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Thu, 2 Jun 2016 12:34:35 -0400 Subject: [PATCH 038/259] Docs: Update Migrate version on download page --- pages/download.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/download.md b/pages/download.md index 9864e87..5b08434 100644 --- a/pages/download.md +++ b/pages/download.md @@ -66,9 +66,9 @@ bower install https://code.jquery.com/jquery-2.2.4.min.js We have created the [jQuery Migrate plugin](https://github.com/jquery/jquery-migrate/#readme) to simplify the transition from older versions of jQuery. The plugin restores deprecated features and behaviors so that older code will still run properly on jQuery 1.9 and later. Use the _uncompressed development_ version to diagnose compatibility issues, it will generate warnings on the console that you can use to identify and fix problems. Use the _compressed production_ version to simply fix compatibility issues without generating console warnings. -Download the compressed, production jQuery Migrate 1.3.0 +Download the compressed, production jQuery Migrate 1.4.1 -Download the uncompressed, development jQuery Migrate 1.3.0 +Download the uncompressed, development jQuery Migrate 1.4.1 ## Cross-Browser Testing with jQuery From cf3c9d6c4e36a82a6f7443c30995a20a6b68c626 Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Thu, 2 Jun 2016 12:35:25 -0400 Subject: [PATCH 039/259] 2.1.26 --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 89d00e8..6abf8d0 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "jquery.com", "title": "jQuery Homepage", - "version": "2.1.25", + "version": "2.1.26", "homepage": "https://github.com/jquery/jquery.com", "author": { "name": "jQuery Foundation and other contributors" From 9220fe0f945bea66b9e81d8cd8dd3595734df939 Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Thu, 9 Jun 2016 12:05:26 -0400 Subject: [PATCH 040/259] Download: Update descriptions and versions for jQuery Migrate --- pages/download.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/pages/download.md b/pages/download.md index 5b08434..037d82e 100644 --- a/pages/download.md +++ b/pages/download.md @@ -64,12 +64,20 @@ bower install https://code.jquery.com/jquery-2.2.4.min.js ## jQuery Migrate Plugin We have created the [jQuery Migrate plugin](https://github.com/jquery/jquery-migrate/#readme) -to simplify the transition from older versions of jQuery. The plugin restores deprecated features and behaviors so that older code will still run properly on jQuery 1.9 and later. Use the _uncompressed development_ version to diagnose compatibility issues, it will generate warnings on the console that you can use to identify and fix problems. Use the _compressed production_ version to simply fix compatibility issues without generating console warnings. +to simplify the transition from older versions of jQuery. The plugin restores deprecated features and behaviors so that older code will still run properly on newer versions of jQuery. Use the _uncompressed development_ version to diagnose compatibility issues, it will generate warnings on the console that you can use to identify and fix problems. Use the _compressed production_ version to simply fix compatibility issues without generating console warnings. + +There are two versions of Migrate. The first will help you update your pre-1.9 jQuery code to jQuery 1.9 up to 3.0. You can get that version here: Download the compressed, production jQuery Migrate 1.4.1 Download the uncompressed, development jQuery Migrate 1.4.1 +The second version helps you update code to run on jQuery 3.0 or higher, *once you have used Migrate 1.x and upgraded to jQuery 1,9 or higher*: + +Download the compressed, production jQuery Migrate 3.0.0 + +Download the uncompressed, development jQuery Migrate 3.0.0 + ## Cross-Browser Testing with jQuery Be sure to test web pages that use jQuery in all the browsers you want to support. The [Microsoft Developer Resources](https://developer.microsoft.com/en-us/microsoft-edge/) site makes available [virtual machines](https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/) for testing many different versions of Internet Explorer. Older versions of other browsers can be found at [oldversion.com](http://oldversion.com/). From 368879d1f994eb8124ddff3be1749d71b41fb900 Mon Sep 17 00:00:00 2001 From: Dave Methvin Date: Thu, 9 Jun 2016 12:06:17 -0400 Subject: [PATCH 041/259] 2.1.27 --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 6abf8d0..c7e16e3 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "jquery.com", "title": "jQuery Homepage", - "version": "2.1.26", + "version": "2.1.27", "homepage": "https://github.com/jquery/jquery.com", "author": { "name": "jQuery Foundation and other contributors" From 248301f7ea5be0fa451e21e9f0f9394a91fbd0fe Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Go=C5=82=C4=99biowski?= Date: Mon, 29 Jun 2015 19:16:10 +0200 Subject: [PATCH 042/259] Browser support: Update the site for jQuery 3.0.0 Closes #103 --- pages/browser-support.html | 23 ++++++++++++----------- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/pages/browser-support.html b/pages/browser-support.html index a41d565..1b8f255 100644 --- a/pages/browser-support.html +++ b/pages/browser-support.html @@ -9,33 +9,34 @@

Current Active Support

Internet Explorer - Chrome, Edge, Firefox + Edge + Chrome, Firefox, Opera Safari - Opera iOS Android - jQuery 1.x - 6+ - (Current - 1) or Current - 5.1+ - 12.1x, (Current - 1) or Current + jQuery + 9+ + Current + (Current - 1) and Current + 6.0+ 6.1+ 2.3, 4.0+ - jQuery 2.x - 9+ + jQuery Compat + 8+

Any problem with jQuery in the above browsers should be reported as a bug in jQuery.

-

(Current - 1) or Current denotes that we support the current stable version of the browser and the version that preceded it. For example, if the current version of a browser is 24.x, we support the 24.x and 23.x versions.

-

12.1x, (Current - 1) or Current denotes that we support Opera 12.1x as well as last 2 versions of Opera. For example, if the current Opera version is 20.x, we support Opera 12.1x, 19.x and 20.x but not Opera 15.x through 18.x.

+

(Current - 1) and Current denotes that we support the current stable version of the browser and the version that preceded it. For example, if the current version of a browser is 24.x, we support the 24.x and 23.x versions.

+

Current denotes that we support only the latest stable build of the browser.

+

If you need to support older browsers like Internet Explorer 6-7, Opera 12.17 or Safari 5.1, use jQuery 1.11.3.

---

Unsupported Browsers

From b66eaba41ecffc419a778c48323d0bd6d665a08d Mon Sep 17 00:00:00 2001 From: Oleg Gaidarenko Date: Sat, 11 Jul 2015 01:30:57 +0300 Subject: [PATCH 043/259] Browser support: Add Yandex.Browser to the list Closes gh-106 --- pages/browser-support.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/browser-support.html b/pages/browser-support.html index 1b8f255..698142e 100644 --- a/pages/browser-support.html +++ b/pages/browser-support.html @@ -9,7 +9,7 @@

Current Active Support

Internet Explorer - Edge + Edge, Yandex.Browser Chrome, Firefox, Opera Safari iOS From 88e9bd359a785eb287019990840ef02e9dc32dd7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Go=C5=82=C4=99biowski?= Date: Fri, 17 Jul 2015 21:29:34 +0200 Subject: [PATCH 044/259] Browser support: Test only on latest Opera Opera is now just another Chromium-based browser, like Yandex.Browser. It doesn't make sense to test on two Opera versions. Closes #107 --- pages/browser-support.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/browser-support.html b/pages/browser-support.html index 698142e..e58acb0 100644 --- a/pages/browser-support.html +++ b/pages/browser-support.html @@ -9,8 +9,8 @@

Current Active Support

Internet Explorer - Edge, Yandex.Browser - Chrome, Firefox, Opera + Edge, Opera, Yandex.Browser + Chrome, Firefox Safari iOS Android From d63e9be82582f729207987882a60e39984391dfa Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Go=C5=82=C4=99biowski?= Date: Mon, 27 Jul 2015 19:51:39 +0200 Subject: [PATCH 045/259] Browser support: Drop support for Safari 6 & iOS 6 Refs jquery/jquery#2482 --- pages/browser-support.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/browser-support.html b/pages/browser-support.html index e58acb0..71d1bcd 100644 --- a/pages/browser-support.html +++ b/pages/browser-support.html @@ -22,8 +22,8 @@

Current Active Support

9+ Current (Current - 1) and Current - 6.0+ - 6.1+ + 7.0+ + 7.0+ 2.3, 4.0+ @@ -36,7 +36,7 @@

Current Active Support

Any problem with jQuery in the above browsers should be reported as a bug in jQuery.

(Current - 1) and Current denotes that we support the current stable version of the browser and the version that preceded it. For example, if the current version of a browser is 24.x, we support the 24.x and 23.x versions.

Current denotes that we support only the latest stable build of the browser.

-

If you need to support older browsers like Internet Explorer 6-7, Opera 12.17 or Safari 5.1, use jQuery 1.11.3.

+

If you need to support older browsers like Internet Explorer 6-7, Opera 12.17 or Safari 5.1-6.0, use jQuery 1.11.3.

---

Unsupported Browsers

From d9c94e73cb56fcdae01fe5bb0efd8d748d3db541 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Go=C5=82=C4=99biowski?= Date: Sun, 2 Aug 2015 22:25:10 +0200 Subject: [PATCH 046/259] Index: Update the browsers list Opera is now a secondary browser (as one of Chromium-likes), Edge is a main one. Also, the desktop list is now sorted alphabetically. Closes gh-109 --- pages/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/index.html b/pages/index.html index 5656bf5..5469f49 100644 --- a/pages/index.html +++ b/pages/index.html @@ -36,7 +36,7 @@

CSS3 Compliant

Cross-Browser

-

IE, Firefox, Safari, Opera, Chrome, and more

+

Chrome, Edge, Firefox, IE, Safari, Android, iOS, and more