StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7477670
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-09-19T21:44:47.023
FavoriteCount
0
LastActivityDate
2011-09-19T21:44:47.023
LastEditDate
LastEditorUserId
0
OwnerUserId
183181
ParentId
7448468
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
<ol> <li><blockquote> Why can't the browser can't reliably capture the mouseout event? If I can reliably tell when the mouse has left the div using the above workaround, why can't the browser do it? </blockquote> I think you answered this one yourself when you said: <blockquote> Compared to letting the browser do all this natively, performing calculations on every pixel move is a bit of a performance hit. </blockquote> The browser does not interpolate between the frames, thus, as you stated it would demand a lot more resources and memory, which may be why it isn't "fixed".</li> <li><blockquote> If some pixel movements are missed just as the mouse crosses the boundary of the div, why does it follow that the mouseout event should also be skipped? When the browser finally starts registering the mouse's position again (after a sudden fast movement), even if the mouse is now miles outside the box, the point is that it used to be in the box and no longer is. So why doesn't it then fire the mouseout event then? </blockquote> I don't know for sure, but I don't think it's a condition of "it was in and now it's out". Instead, it's whether it crosses that boundary (if <code>MouseX - ElemOffsetX= 1</code>). I agree, it doesn't make as much sense, but it could be because if you set the value to <code>> 1</code> it would trigger the event multiple times. Otherwise it would have to keep track of the events, which is not in JS nature, seeing how it just adds events asynch to a stack.</li> </ol> <hr> What you could try is using <a href="http://api.jquery.com/mouseleave/" rel="nofollow">jQuery's mouseleave event</a>. This does two things, which delays the firing of the event: <ol> <li>It traverses the DOM tree to see if it truly left the element</li> <li>I think it implements a timeout call, which should solve the interpolation problem that you noticed.</li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy can't I reliably capture a mouseout event?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USvol7ron
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.