StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POActual Mobile Resolution
primarykey
Id
18994187
data
AcceptedAnswerId
19086339
AnswerCount
2
ClosedDate
CommentCount
5
CommunityOwnedDate
CreationDate
2013-09-25T00:16:03.510
FavoriteCount
0
LastActivityDate
2013-09-30T04:11:12.893
LastEditDate
2013-09-25T00:23:29.093
LastEditorUserId
1138263
OwnerUserId
1138263
ParentId
0
PostTypeId
1
Score
5
ViewCount
3487
LastEditorDisplayName
text
Body
I'm new to HTML5 & CSS3 so I'm working on a simple project to learn it better. I recently discovered responsive design so I am creating a page that scales to my phone. I using media queries, I created two states, one for screens 640px (mobile) and smaller and one for screen 641px and bigger (desktop). The site works fine, showing the correct styles on my desktop when I scale the window and showing the correct style when I view it on my phone. However, after running the site, I decided to check the resolution of my HTC One - it's 1080p. My phone displays the 640px site regardless of orientation. I'm wondering why this happens; the phone's higher resolution shouldn't trigger the mobile state, but it does. I'm thinking I might be confused on how resolutions actually work. So, how do I determine the true resolution of phones (and tablets) so that I can create appropriately scaled sites for them? <pre><code>//Mobile @media screen and (max-width: 640px) { ... } //Desktop @media screen and (min-width: 641px) { ... } </code></pre> Edit Thanks to JoshCs comment below, I realized that I had the viewport meta tag in use from a tutorial. I'd like to revise my question to ask: how does the viewport tag determine what resolution to display for any given device (how do I determine the viewported resolution based on the dimensions of a device)? <pre><code><meta name="viewport" content="width=device-width; initial-scale=1.0"> </code></pre>
Tags
<html><css><html5><css3><mobile>
Title
Actual Mobile Resolution
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USDragonseer
UserOwnerUserId
1. USDragonseer
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
3. 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
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POActual Mobile Resolution
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POActual Mobile Resolution
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POActual Mobile Resolution
 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.