StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17988465
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-01T08:10:09.083
FavoriteCount
0
LastActivityDate
2016-06-19T14:04:48.907
LastEditDate
2017-05-23T12:02:18.240
LastEditorUserId
-1
OwnerUserId
1709587
ParentId
15769282
PostTypeId
2
Score
15
ViewCount
0
LastEditorDisplayName
text
Body
Short answer: it's not possible. Longer answer: XPath can look at HTML attributes, but it can't look at DOM properties. Selecting an <code><option></code> element in a <code><select></code> changes the <code>selected</code> property of the <code><option></code> to <code>true</code>, and also changes the <code>value</code> property of its parent <code><select></code> element, but it doesn't affect the attributes of either, so it is invisible to XPath. To find <code><option></code> elements that have the <code>selected</code> attribute set, which is often how a page author might determine which option is initially selected, you can use <code>//option[@selected]</code>. But this does not find the currently selected <code><option></code>; changes that the user makes to the selection are invisible to XPath. There's no guarantee it will even find the initially selected option, since it's possible that the page author didn't put the <code>selected</code> attribute on any elements and either let the browser select the first option by default or had some JavaScript select the initial option via the <code>selected</code> property. The multiple <a href="https://stackoverflow.com/a/17132439/1709587">other</a> <a href="https://stackoverflow.com/a/17992485/1709587">answers</a> <a href="https://stackoverflow.com/a/27642105/1709587">here</a> <a href="https://stackoverflow.com/a/15769357/1709587">claiming</a> that a selector like <code>//option[@selected]</code> can detect selection changes made by the user after the page loads are simply completely wrong. Of course, if you're able to use CSS selectors instead of XPath selectors, then <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/:checked" rel="noreferrer"><code>option:checked</code></a> will do the job.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFind CURRENTLY selected <option> with XPath
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USMark Amery
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POFind CURRENTLY selected <option> with XPath
 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
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.