jQuery 1.10 Beta 1 Released
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
- #13752: tabIndex propHook’s default value for non-focusable elements should be -1
- #12072: Remove Firefox deprecated nodeValue, getAttributeNode, specified
- #13776: License comment is breaking the SourceMap
- #13755: Update .jshintrc to match style guide
- #13741: Make wrap*/unwrap methods an optional module
- #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
- #13554: Move [un]bind & [un]delegate to event-alias
- #13393: .focus() results in ‘Unspecified error.’ IE9, v1.9
- #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
- #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
> #13744: Move jQuery.fn.size to deprecated
When deprecating functionality, please also describe what replaces it…
So this is replaced by $.fn.width and $.fn.height, or…?
Btw, I still it would have been better to release something like “jQuery lite” and “jQuery full”, instead of two different version. Using the 1.x branch feels like using an older version. I know it isn’t, but it feels wrong. I want to use the “newest” version, but I can’t.
Too confused between the versions of 1.1 and 2.0. Which one is the latest version of the jquery we should use? The back and forth of the version definition change may lead unnecessary energy to follow.