StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
643175
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-03-13T15:14:44.693
FavoriteCount
0
LastActivityDate
2009-03-13T15:14:44.693
LastEditDate
LastEditorUserId
0
OwnerUserId
10199
ParentId
642991
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
That is a great example of someone missing the whole point of avoiding the use of tables for layout. The primary problem with using tables for layout is that it makes it very difficult and tedious to change anything on a site wide scale later. By putting the CSS rules inside the HTML, they are combining the inflexibility of tables with dodgy and repetitive CSS. To top it all off, they are misusing javascript to recreate functionality that already exists in tables. There's not simple or "correct" answer to this question. Without knowing the specifics of your situation, all I can do is lay out a few basics: <ul> <li>Less code is almost always better.</li> <li>If you find yourself trying to replicate table behaviour using css (or especially javascript) you may want to just use tables.</li> <li>Less code is almost always better.</li> <li>If you find yourself nesting tables inside of other tables, there's likely a better way to accomplish your goal.</li> <li>Less code is almost always better.</li> <li>Don't be afraid to change your design a bit if it lets you simplify your code a lot.</li> </ul> The truth is that there are no magic bullets. There are tons of resources out there, but as with any worthwhile pursuit it takes time and dedication. Using a tool that hides the complexity may help in the short term, just be aware that you no longer have control of the trade-offs being made on your behalf behind the scenes. A few places to start: <ul> <li><a href="http://www.456bereastreet.com/archive/200410/bring_on_the_tables/" rel="nofollow noreferrer">http://www.456bereastreet.com/archive/200410/bring_on_the_tables/</a></li> <li><a href="http://www.alistapart.com/topics/code/css/" rel="nofollow noreferrer">http://www.alistapart.com/topics/code/css/</a></li> <li><a href="http://getfirebug.com/" rel="nofollow noreferrer">http://getfirebug.com/</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat's the correct way for a cross-browser HTML layout?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UStgecho
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.