Put down the egg nog and get ready to test. The latest (and most likely last) betas of jQuery 1.11 and 2.1 are now submitted for your inspection and approval. You can get them here:

• http://code.jquery.com/jquery-1.11.0-beta3.js
• http://code.jquery.com/jquery-2.1.0-beta3.js

We know you’ve got a few days off over the holidays, so give us a big present and help us test! Don’t forget that jQuery 1.x supports IE 6/7/8 and jQuery 2.x does not. In other ways the two versions should echo the same feature sets, so it should be possible to switch between the two without too much trouble.

Notable changes

Asynchronous Module Definition (AMD): jQuery components are now built with AMD. jQuery has supported having the library itself loaded by an AMD loader ever since version 1.7. Now, we’re using AMD internally as well, replacing our old modular build system. If you want to know more, see the README file.

Published on npm: The 2.x branch of this beta and all our future 2.x releases will be published on npm so that you can use it with node or packages like browserify. If you want to install the beta, you can use npm install jquery@2.1.0-beta3.

Still to come: No global for the npm version: After polling potential npm/browserify users, we have decided to keep the global namespace clean and not to expose the jQuery global in these situations. Instead, you can do it yourself with window.jQuery = window.$ = require("jquery"). That ticket didn’t make it into the beta, but you should assume you’ll need to set it yourself.

Performance: Our new “lazy feature detects” reduce the startup time for the library, which is especially good for mobile devices. If you never call the API, you never even need to run that code! We also found and removed some situations where jQuery unnecessarily forced a page layout to occur.

Bug fixes: Lots and lots of bug fixes are in this release, including several to ensure the latest versions of browsers like IE11 work smoothly and eliminate console warnings in Chrome. Many fixes are shared across both versions. You can see the complete changelog below.

Breaking changes: None! We’re committed to making this an easy update for you if you already did an upgrade to 1.9+ or are using the jQuery Migrate plugin. So don’t be a chicken, test this beta!

Release Notes

Twas the week before Christmas, when all through the house
Not a creature was stirring, not even a mouse.
The code was checked by the team with such care,
In hopes that a new beta soon would be there.

Contributors nestled all snug in their beds,
While visions of working code danced in their heads.
The pull requests landed, commits all now pushed,
GitHub issues closed, the whole team is bushed.

When on the CDN there arose such a clatter,
I sprang from the bed to see what was the matter.
Away to the laptop I flew like a flash,
Popped open a window and started up bash.

My wondering eyes barely processed the data,
It’s release 3 of jQuery 1.11 and 2.1 beta!

And then, on the roof, I heard at the ready,
The loading of code that was solid and steady.
As I drew in my head, and was turning around,
Down the chimney St. jQuery came with a bound.

“I’m needing your help,” St. jQuery exclaimed,
“If we ship code with bugs I know I’ll be flamed!”
“Just run this beta with your best sites and apps,
so we know if our changes avoided the traps.”

More rapid than eagles contributors came,
He whistled, and shouted, and thanked them by name!
“Now Timmy! now, Richard! now Micha&#322 and John!
On Oleg! On Chris! On Jakob and Hong!
To the top of the list, your reward won’t be small!
Now cache away! Cache away! Cache away all!”

He sprang to his sleigh, to his team gave a whistle,
And away they all flew like the down of a thistle.
But I heard him exclaim, as he drove out of sight,
“Happy beta to all, and to all a good-night!”

Changelog

Common to both jQuery 1.11 Beta 3 and jQuery 2.1 Beta 3

Ajax

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

Attributes

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

Build

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

Core

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

Css

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

Data

• #14101: JQUERY 1.10’S .DATA() RESULT DIFFERS FROM 1.8 WHEN ATTEMPTING TO GET DATA FROM A NON-EXISTENT OBJECT.
• #14459: data-* attribute parsing bypasses jQuery.parseJSON (inconsistent with 1.x)

Effects

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

Event

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

Selector

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

Support

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

jQuery 1.11 Beta 3

Ajax

• #14475: Local Ajax requests don’t work in IE 11 (ActiveXObject checking in jQuery fails)

Core

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

Effects

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

Support

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

jQuery 2.1 Beta 3

Ajax

• #14207: Ajax error defaults to status 404

Build

• #13768: Error trying to load jQuery from node.js

Core

• #14313: Optimize jQuery.merge for size

Event

• #14544: Remove elem reference from event handler

Unfiled

• #14340: Remove oldIE code from support tests on master

The latest betas of jQuery 1.11 and 2.0 have arrived! You can get them here:

• http://code.jquery.com/jquery-1.11.0-beta2.js
• http://code.jquery.com/jquery-2.1.0-beta2.js

Don’t forget that jQuery 1.x supports IE 6/7/8 and jQuery 2.x does not.

What’s in the beta

Asynchronous Module Definition (AMD): The biggest change in 1.11/2.1 continues to be AMD. jQuery has supported having the library itself loaded by an AMD loader ever since version 1.7. Now, we’re using AMD internally as well, replacing our old modular build system. If you want to know more, read the README file.

Published on npm: The 2.x branch of this beta and all our future 2.x releases will be published on npm so that you can use it with node or packages like browserify. Note that the main jquery page is currently not up to date, and won’t be until we push the final 2.1.0 to it. If you want to install the beta, you can use npm install jquery@2.1.0-beta2. Many thanks to Domenic Denicola who has already reported bugs #14548 and #14549 that will be fixed in the next go-round.

Performance: Our new “lazy feature detects” reduce the startup time for the library, which is especially good for mobile devices. If you never call the API, you never even need to run that code! We also found and removed some situations where jQuery unnecessarily forced a page layout to occur.

Bug fixes: Lots and lots of bug fixes are in this release, including several to ensure the latest versions of browsers like IE11 work smoothly and eliminate console warnings in Chrome. Many fixes are shared across both versions. You can see the complete changelog below.

Breaking changes: None! We’re committed to making this an easy update for you if you already did an upgrade to 1.9+ or are using the jQuery Migrate plugin.

Please do give these betas a try and let us know whether everything is working as you’d like. It’s always frustrating to us when we make a new production release and people find bugs that could have been fixed during the beta process. It only takes a few minutes to smoke-test your code against these betas, and it will save both you and us a lot of future heartache!

Sad sourcemap story

One of the changes we’ve made in this beta is to remove the sourcemap comment. Sourcemaps have proven to be a very problematic and puzzling thing to developers, generating scores of confused questions on forums like StackOverflow and causing users to think jQuery itself was broken.

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

We will be encouraging browser makers to come up with better ways to handle sourcemaps for situations like jQuery’s, where there are widely distributed files on CDNs. We’d like sourcemaps to be robust and gracefully handle situations like file renaming or missing files. See our bug ticket for more information.

Let’s give thanks

As Thanksgiving Day approaches, let’s give a hand to the great people who have contributed to jQuery core code since the last release: Amey Sakhadeo, Anthony Ryan, Chris Antaki, Chris Price, Corey Frang, Daniel Herman, Dominik D. Geyer, George Kats, Guy Bedford, Ilya Kantor, Jeremy Dunck, Jörn Zaefferer, Lihan Li, Marian Sollmann, Michał Gołębiowski, Mike Sidorov, Noah Hamann, Oleg Gaidarenko, Richard Gibson, Ronny Springer, Scott González, Sindre Sorhus, Terry Jones, Timmy Willison, and Timo Tijhof.

jQuery 1.11 and 2.1 Beta 2 Changelog (common to both)

Ajax

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

Attributes

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

Build

• #12757: Enforce style guide via build process
• #13983: Switch to //# for sourcemap directives
• #14113: AMD-ify jQuery source
• #14118: Use bower to include Sizzle and QUnit (remove submodules)
• #14163: Make Deferreds/Callbacks/.ready() optional modules
• #14415: Remove sourcemap comment
• #14450: Remove CommonJS+AMD syntax from source

Core

• #14164: Reduce forced layout reflows in init or methods
• #14492: parseJSON incorrectly accepts comma expressions

Css

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

Data

• #14101: JQUERY 1.10’S .DATA() RESULT DIFFERS FROM 1.8 WHEN ATTEMPTING TO GET DATA FROM A NON-EXISTENT OBJECT.
• #14459: data-* attribute parsing bypasses jQuery.parseJSON (inconsistent with 1.x)

Effects

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

Event

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

Selector

• #14142: Wrong number of elements returned in XML document with numeric IDs in Safari
• #14351: Exception thrown when running `find` in a non-attached DOM node
• #14535: Selection fails in IE11 when the last context is a no-longer-present iframe document

Support

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

jQuery 1.11 Beta 2

Ajax

• #14475: Local Ajax requests don’t work in IE 11 (ActiveXObject checking in jQuery fails)

Core

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

Effects

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

Support

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

jQuery 2.1 Beta 2

Ajax

• #14207: Ajax error defaults to status 404
• #14424: ajax with isLocal=true flag in IE

Build

• #13768: Error trying to load jQuery from node.js
• #14340: Remove oldIE code from support tests on master

Core

• #14313: Optimize jQuery.merge for size

Event

• #14544: Remove elem reference from event handler

Ahoy Matey! Do you know what today is? It’s Talk Like a Pirate Day!

Before the jQuery team weighed anchor and ran for the grog, we left a treasure chest on the jQuery CDN filled with beta versions of jQuery 1.11 and 2.1. Here be the treasure map to the bounty:

• http://code.jquery.com/jquery-1.11.0-beta1.js
• http://code.jquery.com/jquery-2.1.0-beta1.js

Don’t forget that jQuery 1.x supports IE 6/7/8 and jQuery 2.x does not. Here are the highlights of what changed:

Asynchronous Module Definition (AMD): In this release we’re going full-mast with AMD. jQuery has supported having the library itself loaded by an AMD loader ever since version 1.7. Now, we’re using AMD internally as well, replacing our old modular build system. Colin Snover started it with some fine cutlass work, then Timmy Willison made sure the whole library was drawn and quartered properly with AMD. He even mollycoddled you with a fine README file so you can be buildin’ yer own custom version. And because we’re pirates, we’re using aaaarrrrr.js to build it.

Performance: Michał Gołębiowski led the charge to reduce jQuery’s startup time by deferring much of the feature detection code so that it runs the first time you use an API call, rather than on page load. If you never call the API, you never even need to run that code! We also found and removed some situations where jQuery unnecessarily forced a page layout to occur.

Bower support: We’re now using Bower for a lot of our internal dependency management, and plan to publish production versions of jQuery to Bower in the future.

Bug fixes: We keelhauled a few scurvy bugs since the last versions. There’s a list down the way if you want to be knowin’.

API changes: None! With all the internal code changes for AMD, we didn’t want to change a lot of APIs in this version. Your old scurvy code should work with no problems as long as you already did an upgrade to 1.9+ or are using the jQuery Migrate plugin.

Now we know some of you may not be takin’ the time to try this beta. We got a name for you: bilge rats. Don’t be comin’ to us after the release and complainin’ about bugs. Get on board and man the lines so we can get this code shipshape before the beta is over!

A tip of the pirate hat to the sea dogs and scallywags who got this release under way: Timmy Willison, Michał Gołębiowski, Oleg Gaidarenko, Richard Gibson, Amey Sakhadeo, Jörn Zaefferer, Chris Price, Daniel Herman, Guy Bedford, Jeremy Dunck, Mike Sidorov, and Terry Jones. And of course an aye-aye shout-out to the original jQuery pirate, Long John Resig!

jQuery 1.11 and 2.1 Changelog (common to both)

Ajax

• #14356: Remove string indexing used in AJAX

Attributes

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

Build

• #13983: Switch to //# for sourcemap directives
• #14113: AMD-ify jQuery source
• #14118: Use bower to include Sizzle and QUnit (remove submodules)
• #14163: Make Deferreds/Callbacks/.ready() optional modules

Core

• #14164: Reduce forced layout reflows in init or methods

Css

• #14150: IE9-10 curCSS => “Interface not supported” in for popups (and probably frames)

Effects

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

Event

• #14282: Don’t call getPreventDefault() if there is a defaultPrevented property

Selector

• #14351: Exception thrown when running `find` in a non-attached DOM node
• #14142: Wrong number of elements returned in XML document with numeric IDs in Safari

Support

• #10814: make support as lazy as possible with closure in mind
• #14084: elem.css(‘width’) provides incorrect output with `box-sizing: border-box` if run before document ready

jQuery 2.1

Build

• #13768: Error trying to load jQuery from node.js

Core

• #14313: Optimize jQuery.merge for size

jQuery 1.11

Effects

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

It’s nearly Independence Day here in the USA, so we’re delivering something fresh off the grill: jQuery 1.10.2 and 2.0.3. These releases fix a few pesky bugs that have been reported over the past month, but the list is refreshingly small. Since some of the bugs spanned both the 1.x and 2.x branches we’re releasing new versions of both to keep them in sync.

You can get the latest files from the jQuery download page, including sourcemap files and links to helpful tools such as jQuery Migrate. If you’re upgrading from a version of jQuery before 1.9, please do read through that page carefully to make your migration as pain-free as possible. Remember that it may take a few days for the CDNs at Google, Microsoft, and CDNJS to respond to the rocket’s red glare and post the latest versions. In the meantime, use the copy on the jQuery CDN.

We’re pretty optimistic that these latest bug-fix releases should be free of surprises. If you drop the new files into your site and see fireworks, please do your patriotic duty and report a bug with a test case (preferably using jsFiddle) at our bug tracker.

These releases wouldn’t have happened without the contributions of Jason Bedard, Jason Merino, Jörn Zaefferer, Michał Gołębiowski, Nguyen Phuc Lam, Oleg Gaidarenko, Richard Gibson, Rick Waldron, Terry Jones, and Timmy Willison.

jQuery 1.10.2 and 2.0.3 Changelog (common to both)

Build

• #13371: Update node-testswarm to 1.0

Css

• #14049: -webkit-order doesn’t work with css()

Selector

• #13974: Accessing XML attribute named “type” broken on IE 7
• #13980: JQuery library does not load in Opera 12.15 and IE 10 in IFrame which content is loaded from external domain

jQuery 2.0.3 Changelog (specific to 2.x)

Data

• #14047: $.data() can’t retrieve data stored by .data() when key is hyphenated

Manipulation

• #13976: Invalid HTML passed into .html() throws ‘tmp is null’ error

A new release already? It’s only been a week! Yes, because you deserve it. We’re greatly encouraged by all the people who upgraded and found our well-hidden “we completely hosed relative animations” easter egg. This release restores += animations and friends to their former glory, plus it fixes a few smaller bugs that were reported. Since the bug affected both the 1.x and 2.x branches, we’re doing new releases for both.

As always, you can get the latest files from the jQuery download page, including sourcemap files and links to helpful tools such as jQuery Migrate. Thank you Tom Byrer for pointing out that the sourcemap files weren’t listed on the download page, and also for contacting the CDNJS folks to have them host the sourcemap files.

Many thanks to jQuery team members Corey Frang, Oleg Gaidarenko, and Richard Gibson for quickly jumping on these issues and creating unit tests to prevent future regressions. This ensures we never make the same mistake twice, but instead deliver fresh and unique bugs with each release. If you find any of those, please report them with a test case (preferably using jsFiddle) at our bug tracker.

I hope that we’ll see many of you at the jQuery Conference Portland, coming up just two weeks from now!

jQuery 1.10.1 and 2.0.2 Changelog

Effects

• #13937: finish() only finishes last item of a set being .animate()d.
• #13939: 1.10.0 breaks relative animation

Selector

• #13936: SCRIPT70 Permission denied in selectors after iframe was submitted in IE9-10, jQuery 1.9.1 and 2.0.0

It’s a wonderful day for a software release. Such a wonderful day, we’re doing two software releases! Today it’s jQuery 1.10.0 and jQuery 2.0.1 making their debut — five years to the day after jQuery 1.2.6 was released.

A simultaneous release isn’t always easy, but it can be very satisfying. The team is certainly satisfied with this duo of deliveries; those of you who have already upgraded to the 1.9/2.0 level should have an easy time with these versions. If you’re upgrading older code, the advice in the jQuery 1.9 upgrade guide still applies to these two releases as well. Also don’t forget that jQuery. 2.0 doesn’t support IE 6, 7, or 8 since we’re leaving that work to the 1.x branch. If you need some help updating or keeping older pre-1.9 jQuery code going, don’t forget about the jQuery Migrate plugin.

As always, the latest versions are all available on our download page.

What’s new? Our main goal with these two releases is to synchronize the features and behavior of the 1.x and 2.x lines, as we pledged a year ago when jQuery 2.0 was announced. Going forward, we’ll try to keep the two in sync so that 1.11 and 2.1 are feature-equivalent for example. We don’t anticipate you’ll find any of these to be disruptive changes. Here are a few highlights:

Relaxed HTML parsing: You can once again have leading spaces or newlines before tags in $(htmlString). We still strongly advise that you use $.parseHTML() when parsing HTML obtained from external sources, and may be making further changes to HTML parsing in the future.

Increased modularity: In either version, you now can do a custom build that excludes the .wrap(), .wrapAll(), .wrapInner() and .unwrap() methods. If all your code is using the newer .on() event methods introduced in jQuery 1.7, you can also exclude .bind() and .delegate() as well. The builds available on the jQuery, Google, and Microsoft CDNs continue to include all methods to provide maximum compatibility.

No more IE9 focus of death: If a page inside an iframe attempts to focus an element or even tries to read document.activeElement before the page is ready, it causes an error. We now work around this issue.

Cordova bug fix in 2.0.1: The Cordova deviceready event doesn’t properly set an event target, so we work around the problem by setting the target to document.

Many thanks to the people who contributed work to jQuery 1.10.0 or jQuery 2.0.1: Brandon Johnson, Chris Talkington, Dmitry Gusev, James Burke, Jason Bedard, Julian Aubourg, Kyle Robinson Young, Mark Raddatz, Michał Gołębiowski, Nguyen Phuc Lam, Oleg Gaidarenko, Renato Oliveira dos Santos, Richard Gibson, Rick Waldron, Scott González, Timmy Willison, Timo Tijhof, and Tom H Fuertes.

jQuery 1.10.0 Changelog

Ajax

• #13922: HEAD responses with application/json results parseerror
• #13388: Ajax request not returning responseXML

Attributes

• #13835: hasClass fails when class contains form feed
• #13809: Closure Compiler/YUI Compressor fail
• #13752: tabIndex propHook’s default value for non-focusable elements should be -1
• #13514: Setting “wrong” value of select-element using .val() is inconsistent in IE9 compared to other browsers
• #12072: Remove Firefox deprecated nodeValue, getAttributeNode, specified

Build

• #13741: Make wrap*/unwrap methods an optional module
• #13755: Update .jshintrc to match style guide
• #13776: License comment is breaking the SourceMap
• #13793: SourceMap on Google is broken

Core

• #12199: $.isPlainObject false positive in IE < 9
• #13223: JQUERY 1.9 + CLIENT-SIDE TEMPLATE = “SYNTAX ERROR, UNRECOGNIZED EXPRESSION”
• #13744: Move jQuery.fn.size to deprecated

Event

• #13554: Move [un]bind & [un]delegate to event-alias
• #13393: .focus() results in ‘Unspecified error.’ IE9, v1.9

Manipulation

• #13401: .replaceWith( “” ) with empty string not working
• #13596: .replaceWith should always remove the context set
• #13721: remove(“:nth-child(1)”) works differently than filter(“:nth-child(1)”).remove()
• #13722: replaceWith argument handling is inconsistent with other manipulation methods

Selector

• #13331: jQuery.fn.add returns incorrect order in Chrome and Safari
• #13420: jQuery 1.9.1 fails to filter SVG parent nodes by class name when using .parent() and .closest()
• #13505: jquery#add: seems to get items in collection out of order on larger lists
• #13777: IE7 jQuery attribute selector not working properly
• #13894: .children does not return direct child, but .find does [Firefox only]

Support

• #12040: Test against Content Security Policy (CSP)
• #13743: Remove jQuery.support.boxModel
• #13754: jQuery doesn’t work in a non-HTML document in UAs that have innerHTML on Element and create non-HTML elements via createElement

Traversing

• #13265: parent method fails with text nodes in IE10
• #13332: .closest(“*”) yields input even for non-element nodes

jQuery 2.0.1 Changelog

Ajax

• #13922: HEAD responses with application/json results parseerror

Attributes

• #13809: Closure Compiler/YUI Compressor fail

Data

• #13815: Setting data property with data(object) produces different results than data(key, value)
• #13850: .data() and removeData() doesn’t work correctly with hyphenated property

Effects

• #13855: Problems animating line-height property

Event

• #13554: Move [un]bind & [un]delegate to event-alias
• #13255: jQuery 2.0b1 and Cordova 2.3.0 cause “Uncaught TypeError: Cannot read property ‘nodeType’ of null”.

Manipulation

• #13803: XMLHttpRequest cannot load
• #13818: Creation of `col` elements inconsistancy

Selector

• #13577: New minimal selector engine fails on textNode objects

Traversing

• #13819: Selection through children results in descending order
• #13846: jQuery 2.0.0 reversing order of returned elements

Today the team is releasing jQuery 1.10 Beta 1. This release should be a relatively easy upgrade for any code that has already been updated for jQuery 1.9/2.0, and it doesn’t introduce a lot of breaking changes–at least not that we know of! That’s why we do beta releases. You tell us.

It may seem like only yesterday that jQuery 1.9 was released, but it was actually all the way back in January. In the meantime, we’ve also delivered jQuery 2.0, the first version of jQuery to leave behind the nightmarish workarounds needed by older versions of Internet Explorer. jQuery 1.10 includes some minor tweaks that we originally introduced in jQuery 2.0, plus bug fixes for issues reported since jQuery 1.9.1.

The biggest change you’re likely to see is that we’ve loosened up the criteria for HTML processing in $(), allowing leading spaces and newlines as we did before version 1.9. We still recommend the use of $.parseHTML() for any HTML coming from external sources. Future versions of jQuery may place tighter restrictions on the kind of markup that $(string) will process, to help you to avoid the ever-present threat of cross-site scripting (XSS) issues.

If you haven’t yet upgraded to the 1.9/2.0 versions yet, catch up by reading the previous blog announcements for jQuery 1.9 and jQuery 2.0. Be sure to check out the jQuery 1.9 Upgrade Guide and the jQuery Migrate plugin.

You can get the beta file here: http://code.jquery.com/jquery-1.10.0-beta1.js

Try this beta code with your most treasured projects and let us know how it works. If you find problems, even when using jQuery Migrate, please report them along with a test case demonstrating the bug at bugs.jquery.com. Please don’t report bugs or ask for help in the blog comments below.

It’s our goal to keep the 1.x and 2.x lines in sync functionally so that 1.10 and 2.0 are equal, followed by 1.11 and 2.1, then 1.12 and 2.2 … well, you see the pattern. Any feature additions or functional changes will happen on these major-point releases. Patch releases will simply fix bugs or bring the two further into sync.

Many thanks to the people who contributed work since 1.9.1 was released: Brandon Johnson, Dmitry Gusev, James Burke, Jason Bedard, Julian Aubourg, Kyle Robinson Young, Mark Raddatz, Michal Golebiowski, Nguyen Phuc Lam, Oleg Gaidarenko, Richard Gibson, Rick Waldron, Scott González, Timmy Willison, Timo Tijhof, and Tom H Fuertes.

jQuery 1.10 Beta 1 Changelog

Attributes

• #13752: tabIndex propHook’s default value for non-focusable elements should be -1
• #12072: Remove Firefox deprecated nodeValue, getAttributeNode, specified

Build

• #13776: License comment is breaking the SourceMap
• #13755: Update .jshintrc to match style guide
• #13741: Make wrap*/unwrap methods an optional module

Core

• #13744: Move jQuery.fn.size to deprecated
• #13223: JQUERY 1.9 + CLIENT-SIDE TEMPLATE = “SYNTAX ERROR, UNRECOGNIZED EXPRESSION”
• #12199: $.isPlainObject false positive in IE < 9

Event

• #13554: Move [un]bind & [un]delegate to event-alias
• #13393: .focus() results in ‘Unspecified error.’ IE9, v1.9

Manipulation

• #13722: replaceWith argument handling is inconsistent with other manipulation methods
• #13721: remove(“:nth-child(1)”) works differently than filter(“:nth-child(1)”).remove()
• #13596: .replaceWith should always remove the context set

Selector

• #13777: IE7 jQuery attribute selector not working properly

Support

• #13754: jQuery doesn’t work in a non-HTML document in UAs that have innerHTML on Element and create non-HTML elements via createElement
• #13743: Remove jQuery.support.boxModel

They say there are no second acts in software … well, there are always second acts in software. Especially when the first act bombs. With that in mind, version 1.2.1 of the jQuery Migrate plugin has arrived. It can be used with either jQuery 1.9 or jQuery 2.0.

This minor update addresses regressions created by the security fix in the 1.2.0 release that rejected some valid HTML strings. Many thanks to GitHub users gerrod, basc, Leonya, krzyko, and lorddefinitia for reporting these issues.

You can find this latest version of the jQuery Migrate plugin on jQuery’s CDN:

• http://code.jquery.com/jquery-migrate-1.2.1.js
  The uncompressed development version provides compatibility and also generates console warning messages that help you find and fix migration issues.
• http://code.jquery.com/jquery-migrate-1.2.1.min.js
  The minified version makes jQuery 1.9/2.0 compatible as possible with older versions, so you can run code in production without warning messages.

Complete instructions and a complete list of the diagnostics given by the plugin are located in the plugin project’s README file.

A full list of all changes are in the issue tracker.