StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6004028
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
8
CommunityOwnedDate
CreationDate
2011-05-14T18:38:55.433
FavoriteCount
0
LastActivityDate
2018-04-27T23:01:51.170
LastEditDate
2018-04-27T23:01:51.170
LastEditorUserId
664833
OwnerUserId
425275
ParentId
6003819
PostTypeId
2
Score
581
ViewCount
0
LastEditorDisplayName
text
Body
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: <pre><code><input type="text" value="Name:"> </code></pre> has 2 attributes (<code>type</code> and <code>value</code>). Once the browser parses this code, a <a href="https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement" rel="noreferrer">HTMLInputElement</a> 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 <code>attributes</code> 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: <pre><code><input id="the-input" type="text" value="Name:"> </code></pre> the corresponding DOM node will have <code>id</code>,<code>type</code>, and <code>value</code> properties (among others): <ul> <li>The <code>id</code> property is a reflected property for the <code>id</code> attribute: Getting the property reads the attribute value, and setting the property writes the attribute value. <code>id</code> is a pure reflected property, it doesn't modify or limit the value.</li> <li>The <code>type</code> property is a reflected property for the <code>type</code> attribute: Getting the property reads the attribute value, and setting the property writes the attribute value. <code>type</code> isn't a pure reflected property because it's limited to known values (e.g., the valid types of an input). If you had <code><input type="foo"></code>, then <code>theInput.getAttribute("type")</code> gives you <code>"foo"</code> but <code>theInput.type</code> gives you <code>"text"</code>.</li> <li>In contrast, the <code>value</code> property doesn't reflect the <code>value</code> attribute. Instead, it's the current value of the input. When the user manually changes the value of the input box, the <code>value</code> property will reflect this change. So if the user inputs <code>"John"</code> into the input box, then: <pre><code>theInput.value // returns "John" </code></pre> whereas: <pre><code>theInput.getAttribute('value') // returns "Name:" </code></pre> The <code>value</code> property reflects the current text-content inside the input box, whereas the <code>value</code> attribute contains the initial text-content of the <code>value</code> 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 <code>defaultValue</code> property, which is a pure reflection of the <code>value</code> attribute: <pre><code>theInput.value // returns "John" theInput.getAttribute('value') // returns "Name:" theInput.defaultValue // returns "Name:" </code></pre></li> </ul> There are several properties that directly reflect their attribute (<code>rel</code>, <code>id</code>), some are direct reflections with slightly-different names (<code>htmlFor</code> reflects the <code>for</code> attribute, <code>className</code> reflects the <code>class</code> attribute), many that reflect their attribute but with restrictions/modifications (<code>src</code>, <code>href</code>, <code>disabled</code>, <code>multiple</code>), and so on. <a href="https://www.w3.org/TR/html5/infrastructure.html#reflect" rel="noreferrer">The spec</a> covers the various kinds of reflection.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat is the difference between properties and attributes in HTML?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USuser664833
UserOwnerUserId
1. USŠime Vidas
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhat is the difference between properties and attributes in HTML?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COHey Sime, I am guessing this is pretty ambiguous, especially if you have a look over here: http://www.w3.org/TR/html4/index/attributes.html, and there is no clear cut answer. One basically needs to follow what is stated in the summary on the jQuery blog and even then, the one will map to the other and work in both instances with a slight performance hit should you incorrectly use prop when you need to use attr
 singulars
 PostPostId
 PO
 UserUserId
 USschalkneethling
2. CO@oss Your link refers to a list of HTML attributes. That list is not ambiguous - those are attributes.
 singulars
 PostPostId
 PO
 UserUserId
 USŠime Vidas

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.