JQuery 1.7 Released

#1

Post by dmethvin » Thu, Nov 03, 2011, 8:28 PM UTC

Re: JQuery 1.7 Released

#2

Post by suyash » Thu, Nov 03, 2011, 8:36 PM UTC

Very interesting, the chart show significant performance gain in IE 7, 8 etc compared to the previous jQuery version. Congratulations.

Re: JQuery 1.7 Released

#3

Post by untog » Thu, Nov 03, 2011, 8:44 PM UTC

There is one ambiguous case: If the data argument is a string, you must provide either a selector string or null so that the data isn’t mistaken as a selector. Pass an object for data and you’ll never have to worry about special cases.

I'm being picky I know, but wouldn't it just be easier to use something like:

    $("#div").on("click", {
      selector: "span",
      data: "blahblah",
      handler: function()
    });

Perhaps it's far too verbose, now that I've typed it out. But it just seems like it would do a good job of removing ambiguities like this.

Re: JQuery 1.7 Released

#4

Post by scarmig » Thu, Nov 03, 2011, 8:48 PM UTC

The best thing is the new, unified event API.

They've also improved event delegation performance by a factor of 2.

Re: JQuery 1.7 Released

#5

Post by ghc » Thu, Nov 03, 2011, 8:49 PM UTC

This makes me so happy. Those of us developing on Chrome 16 have been suffering through a storm of event.layerX/Y deprecation warnings.

This new release fixes the issue and I can confirm the fix works like a charm.

Re: JQuery 1.7 Released

#6

Post by drewda » Thu, Nov 03, 2011, 8:51 PM UTC

Can someone describe to me how these jQuery releases make their way into Rails 3.1 land? Does the maintainer of https://github.com/rails/jquery-rails do an update and then it's up to us Rails users to execute a "bundle update"?

Re: JQuery 1.7 Released

#7

Post by dmethvin » Thu, Nov 03, 2011, 8:53 PM UTC

untog wrote: post #3

There is one ambiguous case: If the data argument is a string, you must provide either a selector string or null so that the data isn’t mistaken as a selector. Pass an object for data and you’ll never have to worry about special cases. I'm being picky I know, but wouldn't it just be easier to use something like: $("#div").on("click", { selector: "span", data: "blahblah", handler: function() }); Perhaps it's far too v…

The data feature isn't used that frequently, and when it is the best way to use it is by passing an object anyway. So although it's mentioned it is likely to be very uncommon.

Re: JQuery 1.7 Released

#8

Post by clarkmoody » Thu, Nov 03, 2011, 8:53 PM UTC

I can't wait for the Closure Compiler extern file for this new version!

Re: JQuery 1.7 Released

#9

Post by kenjackson » Thu, Nov 03, 2011, 8:54 PM UTC

Is there a good set of jQuery tutorials that uses 1.7 (so you don't learn non-best practices)? I know it was just released, but these things are often built along with the development.

Re: JQuery 1.7 Released

#10

Post by dmethvin » Thu, Nov 03, 2011, 9:02 PM UTC

kenjackson wrote: post #9

Is there a good set of jQuery tutorials that uses 1.7 (so you don't learn non-best practices)? I know it was just released, but these things are often built along with the development.

The docs site has a "What's new in jQuery 1.7" section that might help. As far as what is non-best practice, we'll be covering some of that in a blog post next week so stay tuned.