1666 posts Time is what you desire most, but waste carelessly.
  • Sold between 100 000 and 250 000 dollars
  • Elite Author
  • Bought between 50 and 99 items
  • Referred between 100 and 199 users
  • Grew a moustache for the Envato Movember competition
  • Exclusive Author
  • Has been a member for 4-5 years
  • Microlancer Beta Tester
  • Europe
+1 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?

3120 posts
  • Sold between 5 000 and 10 000 dollars
  • United States
  • Bought between 10 and 49 items
  • Has been a member for 3-4 years
  • Exclusive Author
chrisakelley says
1666 posts Time is what you desire most, but waste carelessly.
  • Sold between 100 000 and 250 000 dollars
  • Elite Author
  • Bought between 50 and 99 items
  • Referred between 100 and 199 users
  • Grew a moustache for the Envato Movember competition
  • Exclusive Author
  • Has been a member for 4-5 years
  • Microlancer Beta Tester
  • Europe
+1 more
Firsh says

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

3120 posts
  • Sold between 5 000 and 10 000 dollars
  • United States
  • Bought between 10 and 49 items
  • Has been a member for 3-4 years
  • Exclusive Author
chrisakelley 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

1666 posts Time is what you desire most, but waste carelessly.
  • Sold between 100 000 and 250 000 dollars
  • Elite Author
  • Bought between 50 and 99 items
  • Referred between 100 and 199 users
  • Grew a moustache for the Envato Movember competition
  • Exclusive Author
  • Has been a member for 4-5 years
  • Microlancer Beta Tester
  • Europe
+1 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.

5277 posts The Dude Abides
  • United States
  • Exclusive Author
  • Has been a member for 5-6 years
  • Elite Author
  • Sold between 100 000 and 250 000 dollars
  • Bought between 100 and 499 items
  • Referred between 100 and 199 users
+5 more
CodingJack says

Thanks for the heads up Firsh :)

1666 posts Time is what you desire most, but waste carelessly.
  • Sold between 100 000 and 250 000 dollars
  • Elite Author
  • Bought between 50 and 99 items
  • Referred between 100 and 199 users
  • Grew a moustache for the Envato Movember competition
  • Exclusive Author
  • Has been a member for 4-5 years
  • Microlancer Beta Tester
  • Europe
+1 more
Firsh says

Np.

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

5277 posts The Dude Abides
  • United States
  • Exclusive Author
  • Has been a member for 5-6 years
  • Elite Author
  • Sold between 100 000 and 250 000 dollars
  • Bought between 100 and 499 items
  • Referred between 100 and 199 users
+5 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?

2823 posts
  • Australia
  • Community Moderator
  • Elite Author
  • Author had a Free File of the Month
  • Most Wanted Bounty Winner
  • Author had a File in an Envato Bundle
  • Has been a member for 5-6 years
  • Contributed a Blog Post
  • Repeatedly Helped protect Envato Marketplaces against copyright violations
+10 more
dtbaker Volunteer moderator says

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

by
by
by
by
by
by