StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12606293
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-09-26T16:29:14.223
FavoriteCount
0
LastActivityDate
2014-02-20T21:15:37.753
LastEditDate
2014-02-20T21:15:37.753
LastEditorUserId
678801
OwnerUserId
678801
ParentId
12606245
PostTypeId
2
Score
13
ViewCount
0
LastEditorDisplayName
text
Body
I would use the <code>navigator.useragent</code> property to get the useragent-string, parse it, and detect the OS. <strike><a href="http://www.quirksmode.org/js/detect.html">Here</a> is one example of how you can do it.</strike> Update: Due to the popularity of this question, I thought I would add some additional information to my answer. In general, browser sniffing is almost never the best way to go. Why? Well, there are many reasons, but here are two good ones: <ol> <li>In almost all cases when people turn to browser sniffing, feature detection would be a better option. There are rare edge cases where it might be appropriate to act depending on what OS/browser the user might be using, but for the most part, using a library like <a href="http://modernizr.com/">Modernizr</a> to detect support for a specific feature is a better way to go. Trying to adapt your site/application to specific browsers rather than the features they support is a slippery slope. Instead check if the browser support the features you need, and polyfill or provide nice fallbacks when support is lacking.</li> <li>Browser sniffing is extremely complicated. Why? Because almost every browser lie in their user agent string or lack sufficient information to allow a certain identification.</li> </ol> With that said, if you really really need to use browser/OS detection, then don't reinvent the wheel, and don't try to do it on your own - you will be in for a world of pain and obscure caveats! I would suggest you use a library like <a href="https://github.com/NielsLeenheer/WhichBrowser">WhichBrowser</a>, that will provide you with a handy JavaScript object containing information about the os, browser, rendering engine and device.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODetect if browser is running on an Android or iOS device
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USChristofer Eliasson
UserOwnerUserId
1. USChristofer Eliasson
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.