1829 posts Time is what you desire most, but waste carelessly.
  • Author Level 9
  • Elite Author
  • Exclusive Author
  • Trendsetter
+9 more
Firsh
says

jQuery 1.9 was released nowadays and the deprecated $.browser is not removed. Expect a sh.strom (support requests) because many many many plugins and themes still use this for browser specific behavior. The new alternative is $.support http://api.jquery.com/jQuery.support/

A good example is prettyPhoto that has this check in its source. It’s been updated almost a year ago and still has jQuery 1.6.1 bundled in it. People have been saying not to use $.browser and that it’ll get removed but I’m sure many of us didn’t get the notice. Please update your plugins and themes asap.

The new method is fine and everything but what about those small, nerve-racking things that happen in IE 6-7-8 that are not necessarily due to them not supporting a specific feature, but simply displaying something differently?

3439 posts
  • Author Level 4
  • Collector Level 2
  • Community Superstar
  • United States
+2 more
organicbee
says
1829 posts Time is what you desire most, but waste carelessly.
  • Author Level 9
  • Elite Author
  • Exclusive Author
  • Trendsetter
+9 more
Firsh
says

I see that’s cool, but isn’t it better to code for the new version?

3439 posts
  • Author Level 4
  • Collector Level 2
  • Community Superstar
  • United States
+2 more
organicbee
says

I see that’s cool, but isn’t it better to code for the new version?

yup especially for WP themes as its 1.9 is already in WordPress 3.6 alpha

I just posted the tool so people could fix existing things as it doesnt just restore api for broken things

1829 posts Time is what you desire most, but waste carelessly.
  • Author Level 9
  • Elite Author
  • Exclusive Author
  • Trendsetter
+9 more
Firsh
says

Great I didn’t know about that tool. I’ve just learned you can see what the jQuery team is planning on removing etc ahead of time, so I can check that for the future.

5467 posts The Dude Abides
  • Top Monthly Author
  • Trendsetter
  • Weekly Top Seller
  • United States
+13 more
CodingJack
says

Thanks for the heads up Firsh :)

1829 posts Time is what you desire most, but waste carelessly.
  • Author Level 9
  • Elite Author
  • Exclusive Author
  • Trendsetter
+9 more
Firsh
says

Np.

BTW there is a typo it should say *now removed, instead of *not removed :D

5467 posts The Dude Abides
  • Top Monthly Author
  • Trendsetter
  • Weekly Top Seller
  • United States
+13 more
CodingJack
says

Looking over some of the potential issues:

https://github.com/jquery/jquery-migrate/blob/master/warnings.md

One thing I don’t quite understand is the jQuery.attr() change. Here it says not to use it to read property values:

http://api.jquery.com/attr/

I assume this means a native property of an element? Such as:

var p = $("p").attr("attribute", value);
p[0].property = value;

var val = p.attr("property"); // bad usage
val val = p.prop("property"); // good usage

var attr = p.attr("attribute"); // good usage

Is this correct?

5441 posts
  • Author Level 11
  • Moderator
  • Winner
  • 6 Years of Membership
+20 more
dtbaker
Moderator
says

Yer – removing .live() from jQuery 1.9 just bit me. Ouch! Time to update some scripz!

by
by
by
by
by
by