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?
I see that’s cool, but isn’t it better to code for the new version?
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.
Thanks for the heads up Firsh
BTW there is a typo it should say *now removed, instead of *not removed
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.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?