jQuery 1.7.2 Beta 1 Released

Posted on by

Hey there Internets, it’s the jQuery Core team! We haven’t talked in a while, but over the holidays we were busy fixing the bugs you reported. The result of that hard work is jQuery 1.7.2 Beta 1. We decided to get a beta out by Groundhog Day so you wouldn’t be in the shadow of six more weeks of unfixed bugs.

You can get the code from the jQuery CDN:

Oh, we know what you’re thinking: “Cool, a new version of jQuery; I’ll wait until the final release has been out a few weeks and then I’ll give it a try.” Right, and then you’ll find some bug that keeps you from upgrading. Nothing makes us sadder than finishing up a release and only then seeing a report of a serious bug that could have been fixed earlier.

So please, come out of your burrow and try this beta with your code. Did we miss an old bug? Did we create a new bug that makes you feel like Bill Murray waking up to “I Got You Babe?” We want to know. You can use the bug tracker to report bugs; be sure to create a test case on jsFiddle so we can figure it out easily. If you’re not sure it’s a bug, ask on our forum or on StackOverflow.

jQuery 1.7.2b1 Change Log

The current change log of the 1.7.2b1 release.


  • #10978: jQuery.param() should allow non-native constructed objects as property values


  • #5571: Allow chaining when passing undefined to any setter in jQuery


  • #10692: Configure the jshint options to more accurately match the style guide
  • #10902: ability to test a built version of jQuery in unit tests
  • #10931: Unit tests shouldn’t require internet access


  • #10466: jQuery.param() mistakes wrapped primitives for deep objects


  • #10639: outerWidth(true) and css(‘margin’) returning % instead of px in Webkit
  • #10754: have jQuery.swap return the return of the callback instead of just executing it
  • #10782: Incorrect calculating width
  • #10796: Bug in IE7 with $(‘#el’).css.(‘background-position’)
  • #10858: css.js regular expressions are incomplete
  • #11119: The curCSS function only need 2 arguments


  • #8498: Animate Hooks
  • #10006: method show is not working as expected in all browsers when called for document fragment
  • #10848: Animation toggling loses state tracking in certain atomic edge cases


  • #8165: .live(‘click’, handler) fires on disabled buttons with child elements in Chrome
  • #10819: Eliminate “this.on.call(this, “
  • #10878: $(“select”).live(“change”, function(){ …broken in IE8 in jQuery 1.7
  • #10961: Error in XRegExp using jQuery 1.7.1 in IE6-9
  • #10970: The .on() selector parameter doesn’t work with :not(:first) selector
  • #10984: Cannot off() custom events ($.event.special)
  • #11021: Hover hack mangles a namespace named “hover”
  • #11076: .clone(true) loses delegation filters
  • #11130: jQuery.fn.on: binding map with null selector ignores data
  • #11145: $(document).on() not working with name=”disabled”


  • #9427: Passing undefined to .text() does not trigger setter
  • #10753: inline the evalScript function in manipulation.js as it’s only used once
  • #10864: text() method on a document fragment always returns the empty string
  • #11055: Update HTML5 Shim elements list to support latest html5shiv


  • #10952: .fired() doesn’t work on Callbacks object when it is flagged with “once”
  • #11257: Wrong path to source files in test suite if PHP missing


  • #11048: Support Tests affect layout for positioned elements in IE6-9

18 thoughts on “jQuery 1.7.2 Beta 1 Released

  1. Binarykitten on said:

    D, it’s easy. All you have to do is switch out th e version n that you are using for this one. Run through your code and see if anything breaks. If it does you then check if it’s a plugin that is broken. If it’s a plugin, report the issues to the plugin author. r. If not, then consult the api see if your code is using unexpected behaviour. If that’s not the case, you might have a bug in jQuery. From there, try and see if you can replicate it simply, without your business logic. Use something like jsfiddle. Once you’ve done that, see if your bug has been reported. If not then go ahead and report it.

    I hope this helps.

  2. jQuery Rocks on said:

    The beta works great on the two sites I manage!

    The more intricate site uses jQuery UI 1.8.16 for buttons and accordion menus (need to upgrade it to 1.8.17), and jQuery for AJAX calls, effects, traversing and modifying the DOM, events, and more.

    I’ll test it even further when the final release comes out.

  3. Love jquery. It would be nice if someone can show me how to use ajax call and showing a progress bar indicator. What I’m trying to do is to use ajax to upload the photos to the server but unable to use the onprogress event.

  4. You guys know your Trac system is down, right? At least trying to view the bugs from this blog post gives an error. Has for a few days for me.

  5. Hey there.

    This is a bug in Opera 12.00 (not in earlier versions, but has been there forever in v12), and not in jQuery, but it can be fixed in jQuery. I reported the bug to Opera a few months ago, but they never did anything about it. If you run Opera 12 on any website, Inspect Element, go to the Properties tab on the right pane, then unfold ‘style’, you’ll see that ‘zoom’ is in the list, with an empty value.

    Because jQuery tests for style.zoom to match IE, it will run the IE code path and set style.zoom to 1, which generates a CSS error in Opera.

    As I said — it’s no biggie, but it would still be nice of you if you could do something about it, or even better, complain in an official manner at Opera so that they fix it before their final 12.00 release. You probably have more weight and voice than a single developer. I always have the console opened and it’s an error I’m seeing every time. Thanks :)

  6. Drag and drop partially broke when I upgraded from 1.6 -> 1.7.2 beta. Basically, it became hard to find the ‘sweet spot’ for dropping an image within the drop target rectangle. I don’t know why this is.

  7. jQuery Rocks on said:

    I’m not sure if you’re aware of this, but the jQuery UI blog is marked as a malicious site when I visit it in Firefox… Google has a list of reasons, including distribution of malware by intermediate sites.

    I know this isn’t really related to this blog post, but I wasn’t sure exactly where to post this info.

  8. jQuery Rocks on said:

    Thankfully, the issue with the jQuery UI blog being marked as malicious seems to be resolved now.

  9. What is the correct operation for the “.on” click event handlers? Because ctrl+click won’t open a new tab, but middle click will (so it is not catched).

  10. i have issues with jquery.ui-selectmenu and Firefox 13 (nightly).
    a new “select” appears evertime i call .selectmenu().
    maybe it’s a selectmenu-issue or a jquery&ff13 issue ?!

  11. Martin on said:

    Windows 8 Consumer Preview was also recently released together with IE10 Preview 5, so make sure all tests in v1.7.2 runs OK in this browser.