Earlier quoted context omitted.
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.
I use event data a lot, but I didn’t even realise you could pass a string.
JQuery 1.7 Released
21–30 of 47 posts
Re: JQuery 1.7 Released
#22Anyone have the documentation on jQuery.Callbacks?
http://addyosmani.com/blog/jquery-1-7s-callbacks-feature-dem...
Re: JQuery 1.7 Released
#23Earlier quoted context omitted.
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.
I use event data a lot, but I didn’t even realise you could pass a string.
Re: JQuery 1.7 Released
#24Re: JQuery 1.7 Released
#25Can 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"?
curl http://code.jquery.com/jquery-1.7.js > vendor/assets/javascripts/jquery.js
Re: JQuery 1.7 Released
#26One thing I don't like about jQuery's evolution is the size. This version weights at 92K minified / 33K gzipped, which for mobile phones is a PITA.
Re: JQuery 1.7 Released
#27One thing I don't like about jQuery's evolution is the size. This version weights at 92K minified / 33K gzipped, which for mobile phones is a PITA.
Re: JQuery 1.7 Released
#28Re: JQuery 1.7 Released
#29My favorite part of the release notes: "Despite jQuery.isNaN() being undocumented, several projects on Github were using it. We have contacted them and asked that they use jQuery.isNumeric() or some other solution." This is an excellent reminder of how much things have changed in the last 10 years in our space; a popular tools vendor can go query a massive source code repository and reach out proactively for transiti…
Re: JQuery 1.7 Released
#30There 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.