jQuery 1.8.0 released about jquery-rails HOT 16 CLOSED

+1

from jquery-rails.

This is coming soon. I'm finishing up some backlogged bug-fixes for 1.7 today, and then I'll add support for 1.8.

from jquery-rails.

also jquery-ui and jquery-ujs can be updated too.

from jquery-rails.

@slbug Exactly. I gotta get some bugs fixed with jquery-ujs, then I can add jquery 1.8 support to jquery-ujs, then I can update jquery-rails with 1.8. So, don't fret, it's on its way!

from jquery-rails.

Maybe it will be better to separate jquery-ujs and jQuery for Assets Pipeline? If i use something like https://github.com/kenn/jquery-rails-cdn , but don’t use UJS, I must wait too long for update because of compatibility issues with UJS (unecessary for me) :(.

from jquery-rails.

@ai I don't understand what you're saying. This gem adds jquery-ujs to rails.

from jquery-rails.

I mean that a lot of users use your gem to get just jQuery for Assets Pipeline.

from jquery-rails.

I had no idea anyone was using it for that. The jquery-rails gem has always had the express purpose of including jquery-ujs in your rails app (even before the asset pipeline existed). Core rails ajax functionality actually depends on either prototype-ujs or jquery-ujs (or theoretically any other ujs gem) to work, so I would think the vast majority of people actually use the jquery-rails gem just to make rails work.

But if you are only using jquery (i.e. not using any :remote => true, :confirm, :disable, or :disable_with links/forms/inputs, or any :method => [post|put|delete] links in your entire rails app), you're probably better off just not using the gem and instead putting jquery.js in your vendor/assets/javascripts directory where it will automatically be included in your asset pipeline.

from jquery-rails.

Update to jquery-rails 2.1.0.

from jquery-rails.

Thanks for the prompt update, @JangoSteve! Have some GitHub Karma (omg that's a good idea right there).

from jquery-rails.

Got a really stupid question here, but does anyone have any inkling why it might be the case that I am using jquery-rails 2.1.1 and yet $.fn.jquery is returning 1.7.2? I updated my bundle, and gemfile.lock reflects the update as expected.

from jquery-rails.

@alanhogan did you check the browser cache?

from jquery-rails.

Naturally I did a hard refresh. That should be enough, right, since I am using the asset pipeline, I believe…?

On Aug 22, 2012, at 4:55 AM, Jan Dudulski [email protected] wrote:

@alanhogan did you check the browser cache?

—
Reply to this email directly or view it on GitHub.

Alan Hogan
IFTTT

from jquery-rails.

@alanhogan Hard to say, but something is either cached or misconfigured. I'd make sure that bundle show jquery-rails outputs 2.1.x, restart your rails app, actually clear your browser's cache, and then refresh the page.

from jquery-rails.

Restarting the rails app did it. I should have tried that earlier. Thank you!

On Aug 22, 2012, at 9:13 AM, Steve Schwartz [email protected] wrote:

@alanhogan Hard to say, but something is either cached or misconfigured. I'd make sure that bundle show jquery-rails outputs 2.1.x, restart your rails app, and also actually clear your browser's cache and then refresh the page.

—
Reply to this email directly or view it on GitHub.

Alan Hogan
IFTTT

from jquery-rails.

;-)

from jquery-rails.