StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5138224
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-02-28T04:34:55.463
FavoriteCount
0
LastActivityDate
2011-02-28T04:34:55.463
LastEditDate
LastEditorUserId
0
OwnerUserId
489230
ParentId
4945505
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
It looks like your problem is a combination of things. I've created this updated fiddle to help display the problems: <a href="http://jsfiddle.net/KmMBd/10/" rel="nofollow">http://jsfiddle.net/KmMBd/10/</a> In firefox and IE, Chris is exactly right. Firefox doesn't support the "number" type, so it always treats it as "text". If you load the fiddle, and hit alert it will display "text". Obviously this is incorrect, but firefox doesn't know how to handle the "number" type. If you inspect the input box in firebug, you will see that it does in fact say type="number", and just alerts wrong. This behavior will stay true no matter what kind of toggles or slidetoggles you do. In chrome it looks like a bug. Given that HTML5 is not an official standard yet, this is understandable, and is a wonderful opportunity for a bug report. It looks like Chrome doesn't render the number type correctly when it redraws it. In the fiddle, if you slideToggle 1, and then slideToggle 2, the number spinner will come back. This is what makes me think it is a problem with redrawing it - something with child/parent stuff, I bet. This link has info about reporting bugs in Chrome: <a href="http://www.google.com/support/forum/p/Chrome/thread?tid=2a2135b6f50fd524&hl=en" rel="nofollow">Report Chrome Bugs</a> In safari, the issue is a bit different. The number type is supported, but not actually handled. In short, this means that Safari recognizes that the input is different from a "text" box, but doesn't actually do anything with that information. Essentially, treat Safari the same as Firefox/IE. In short, I guess the true answer to your issue is to avoid number inputs right now. They're not supported in most browsers (just one), and in the ones where they are supported (really, just Chrome) they are buggy. Wait a while - HTML5 will be awesome soon :)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJQuery slideToggle problems
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USjwegner
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.