StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POIn HTML, should block level elements always wrap <a> tags?
primarykey
Id
11434196
data
AcceptedAnswerId
11434315
AnswerCount
4
ClosedDate
CommentCount
7
CommunityOwnedDate
CreationDate
2012-07-11T13:52:21.777
FavoriteCount
3
LastActivityDate
2012-07-12T00:19:01.937
LastEditDate
2017-05-23T12:22:11.210
LastEditorUserId
-1
OwnerUserId
1230663
ParentId
0
PostTypeId
1
Score
8
ViewCount
1397
LastEditorDisplayName
text
Body
<p>In HTML, should block level elements always wrap <code><a></code> tags? What if it's necessary for the tag to wrap the block level element to ensure the correct styles are applied? For example can this</p> <pre><code><h3><a href="/">Your Header</a></h3> </code></pre> <p>be this</p> <pre><code><a href="/"><h3>Your Header</h3></a> </code></pre> <p>NB: I'm going for the latter approach to ensure the correct styles are applied (I'm working with legacy code that is just not worth re-working for this one element), but while doing this I was interested to know what the community's views are.</p> <p>And yes I have read this question <a href="https://stackoverflow.com/questions/5080261/in-html-which-way-round-should-a-and-h1-be-nested">In HTML which way round should a and h1 be nested?</a> but I'm not sure if a different or more flexible rule applies for <code><h3></code> tags.</p> <p>Taking in the comments below and looking again at the code, I have two possible solutions:</p> <ol> <li>Wrap the <code><h3></code> elements with <code><a></code> elements (ok in HTML5)</li> <li>Add <code>.class a</code> to the CSS so that it inherits parent <code>div</code> styles as follows: </li> </ol> <p>HTML</p> <pre><code><div class="class"> <h3><a href="/">Your Header</a></h3> </div> </code></pre> <p>CSS</p> <pre><code>.class, .class a { width:296px; height:46px; overflow:hidden; color:#FE5815; } </code></pre>
Tags
<html><css><html5><xhtml>
Title
In HTML, should block level elements always wrap <a> tags?
singulars
PostAcceptedAnswerId
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USbr3w5
plurals
PostLinksPostIdRelatedPostId
1. PL
  singulars
  LinkTypeLinkTypeId
  LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
2. PO
  singulars
  PostTypePostTypeId
  PTAnswer
3. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  POIn HTML, should block level elements always wrap <a> tags?
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
2. VO
  singulars
  PostPostId
  POIn HTML, should block level elements always wrap <a> tags?
  UserUserId
  USGovind KamalaPrakash Malviya
  VoteTypeVoteTypeId
  VTFavorite
3. VO
  singulars
  PostPostId
  POIn HTML, should block level elements always wrap <a> tags?
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId

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.