Why jQuery 1.9+ attr() method not deprecated?
Can I, a jQuery1.9+ software developer, "deprecate" the use of the attr() method in my day-by-day work?
As showed in many questions,
there are a lot of confusion about "use attr or use prop?", and, by my (developer's) view point, for all uses of attr() method, we can use prop instead:
prop(name,newvalue) method. removeProp(name) method. attr(name) method also affected. About "strong type" of prop: it is better than "html string value" (ex. "checked" vs true). attr in your browser returns undefined if it is not)... Well, we need this in some piece of software? At forms, ".val() method is the recommended jQuery way to get or set the values of form" So, at this time (2013), I not see a good reason to use attr method when developing new jQuery code... But, well, this is, in other words, the question: There are a good reason to use attr method in my day-by-day tasks?
.attr() is not deprecated because it's useful for what it's made for, and is the only correct way to do what it's made for (short of using each element's getAttribute function, which does the same thing...or parsing the HTML yourself). The only reason we are even having this discussion at all is because jQuery (and some old browsers (cough IE cough)) incorrectly conflated attributes and properties, and that muddling is what they apparently fixed in 1.9.
.attr() retrieves attributes, while .prop() retrieves properties. The two are different things, and always officially have been (though the DOM often has a property to correspond to an attribute). If you have a <p whatever="value"> , where whatever is not an attribute the browser recognizes, you'd use .attr() to get the attribute's value. .prop() wouldn't even be able to see it in most browsers.
When you care about the resulting DOM property, use .prop() . When you care about the actual HTML attribute, use .attr() . It's not really an either/or thing; you can use both in the same code and the universe won't implode even once (assuming you've used them correctly, anyway). :) Just use the one that's suited to the job you're doing at the time, and quit trying to "deprecate" stuff that's not broken.
I took the liberty of preparing a fiddle for you:
http://jsfiddle.net/5REVP/
Especially this part:
<div id="example" style="padding:10px"></div>
console.log("style");
var styleAttr = $("#example").attr("style");
console.log(styleAttr); // You get "padding:10px"
var styleProp = $("#example").prop("style");
console.log(styleProp); // You get a CSSStyleDeclaration object
The "style" example shows clearly that an attribute is not the same as a property (check the console).
For readability, maintainability and backward (as well as forward) compatibility you should allways use the correct methods for a given task, otherwise there is a chance that a method may stop behaving as you though it would, the .attr() method is an example of that.
.attr() method is used to get attributes of elements, attributes are a SGML term that refers to the information contained inside the element tags, you can easily read that information by inspecting the elements.
.prop() method is used to get DOM properties of elements.
.attr() only accesses HTML attributes, whereas .prop() will retrieve properties not on the HTML elements. See the documentation:
For example, selectedIndex, tagName, nodeName, nodeType, ownerDocument, defaultChecked, and defaultSelected should be retrieved and set with the .prop() method. Prior to jQuery 1.6, these properties were retrievable with the .attr() method, but this was not within the scope of attr. These do not have corresponding attributes and are only properties.
http://api.jquery.com/prop/
链接地址: http://www.djcxy.com/p/27562.html