What is the difference between properties and attributes in HTML?

 

After the changes made in jQuery 1.6.1, I have been trying to define the difference between properties and attributes in HTML.

Looking at the list on the jQuery 1.6.1 release notes (near the bottom), it seems one can classify HTML properties and attributes as follows:

  • Properties: All which either has a boolean value or that is UA calculated such as selectedIndex.

  • Attributes: 'Attributes' that can be added to a HTML element which is neither boolean nor containing a UA generated value.

    • Thoughts?

    When writing HTML source code, you can define attributes on your HTML elements. Then, once the browser parses your code, a corresponding DOM node will be created. This node is an object, and therefore it has properties.

    For instance, this HTML element: 

    <input type="text" value="Name:">

    has 2 attributes ( type and value ).

    Once the browser parses this code, a HTMLInputElement object will be created, and this object will contain dozens of properties like: accept, accessKey, align, alt, attributes, autofocus, baseURI, checked, childElementCount, childNodes, children, classList, className, clientHeight, etc.

    For a given DOM node object, properties are the properties of that object, and attributes are the elements of the attributes property of that object.

    When a DOM node is created for a given HTML element, many of its properties relate to attributes with the same or similar names, but it's not a one-to-one relationship. For instance, for this HTML element: 

    <input id="the-input" type="text" value="Name:">

    the corresponding DOM node will have id , type , and value properties (among others):

  • The id property is a reflected property for the id attribute: Getting the property reads the attribute value, and setting the property writes the attribute value. id is a pure reflected property, it doesn't modify or limit the value.

  • The type property is a reflected property for the type attribute: Getting the property reads the attribute value, and setting the property writes the attribute value. type isn't a pure reflected property because it's limited to known values (eg, the valid types of an input). If you had <input type="foo"> , then theInput.getAttribute("type") gives you "foo" but theInput.type gives you "text" .

  • In contrast, the value property doesn't reflect the value attribute. Instead, it's the current value of the input. When the user manually changes the value of the input box, the value property will reflect this change. So if the user inputs "John" into the input box, then: 

    theInput.value // returns "John"

    whereas: 

    theInput.getAttribute('value') // returns "Name:"

    The value property reflects the current text-content inside the input box, whereas the value attribute contains the initial text-content of the value attribute from the HTML source code.

    So if you want to know what's currently inside the text-box, read the property. If you, however, want to know what the initial value of the text-box was, read the attribute. Or you can use the defaultValue property, which is a pure reflection of the value attribute: 

    theInput.value                 // returns "John"
theInput.getAttribute('value') // returns "Name:"
theInput.defaultValue          // returns "Name:"

    • There are several properties that directly reflect their attribute ( rel , id ), some are direct reflections with slightly-different names ( htmlFor reflects the for attribute, className reflects the class attribute), many that reflect their attribute but with restrictions/modifications ( src , href , disabled , multiple ), and so on. The spec covers the various kinds of reflection.

    The answers already explain how attributes and properties are handled differently, but I really would like to point out how totally insane this is. Even if it is to some extent the spec.

    It is crazy, to have some of the attributes (eg id, class, foo, bar) to retain only one kind of value in the DOM, while some attributes (eg checked, selected) to retain two values; that is, the value "when it was loaded" and the value of the "dynamic state". (Isn't the DOM supposed to be to represent the state of the document to its full extent?)

    It is absolutely essential, that two input fields , eg a text and a checkbox behave the very same way . If the text input field does not retain a separate "when it was loaded" value and the "current, dynamic" value, why does the checkbox? If the checkbox does have two values for the checked attribute, why does it not have two for its class and id attributes? If you expect to change the value of a text *input* field, and you expect the DOM (ie the "serialized representation") to change, and reflect this change, why on earth would you not expect the same from an input field of type checkbox on the checked attribute?

    The differentiation, of "it is a boolean attribute" just does not make any sense to me, or is, at least not a sufficient reason for this.

    well these are specified by the w3c what is an attribute and what is a property http://www.w3.org/TR/SVGTiny12/attributeTable.html

    but currently attr and prop are not so different and there are almost the same

    but they prefer prop for some things

    Summary of Preferred Usage

    The .prop() method should be used for boolean attributes/properties and for properties which do not exist in html (such as window.location). All other attributes (ones you can see in the html) can and should continue to be manipulated with the .attr() method.

    well actually you dont have to change something if you use attr or prop or both, both work but i saw in my own application that prop worked where atrr didnt so i took in my 1.6 app prop =)

    链接地址: http://www.djcxy.com/p/87986.html

    上一篇: jquery转义方括号来选择元素

    下一篇: HTML中属性和属性有什么区别？