Comments on: iPad and onMouseOver

By: M. Dave Auayan

M. Dave Auayan — Tue, 18 Jan 2011 09:15:00 +0000

It took me a couple readings to figure out what you were asking (and for anyone else reading, he's saying the first link says that the Mobile Safari mouseout event doesn't fire unless you click on a link or form element), however, the second link has a nav element that is hidden on mouseout, which is seems to be triggered by clicking on any element, not just links or form fields).

To possibly answer your question, trung, the first link you posted may have your answer: if you attach an onclick event handler to any element, that element remains focusable even after you remove that handler. I didn't see anything to that effect when trying to view their source, however, so more testing is needed.

By: trung

trung — Tue, 18 Jan 2011 05:10:00 +0000

Hi Dave A question about mouseover / mouseout on ipad , Follow this document http://www.quirksmode.org/blog/archives/2008/08/iphone_events.html . When user focus a element A, mouseover will be fired. mouseout event will be fired when user focus another element B. And in this above link, links and form fields are clickable. Yeahhh. But i visit this page http://www.steadfastcreative.com/ . See the slideshow, when click on slide , NAV will be showed. and when click another element not links ,form fields ,it’s fired mouseout ? why ? trick ?

By: Timo

Timo — Sat, 26 Jun 2010 16:29:18 +0000

What happens if
(a) you put a dummy click-handler in the markup and add the onMouseOver behavior dynamically in jQuery?
(b) you add a dummy click handler and onMouseOver behavior both with jQuery?

By: M. Dave Auayan

M. Dave Auayan — Thu, 06 May 2010 04:15:47 +0000

Indeed, that's exactly what I'm saying, though I haven't run it through any proper tests.

By: tr888

tr888 — Wed, 05 May 2010 22:49:37 +0000

"Sadly, adding those behaviors using jQuery doesn't seem to give it the same magic.".

Are you saying that the onMouseOver eventhandler must be declared in the markup of the served page and cannot be dynamically added to the DOM?

By: Jason

Jason — Tue, 06 Apr 2010 03:15:54 +0000

That's awfully nice of them to stop the propagation. Browsers have been letting events breed like rabbits for far too long.

By: M. Dave Auayan

M. Dave Auayan — Tue, 06 Apr 2010 03:13:52 +0000

You're correct, and I should clarify: it fires those events and stops the click propagation from hitting a link inside the element with the onmouseover event, as is commonly seen on drop down menus.

This behavior is new, not so much the onmouseover events.

By: Jason

Jason — Tue, 06 Apr 2010 02:58:03 +0000

The iPhone has been firing mouseover/out events when the focus changes for awhile now (if not always). It may be inappropriately named, but I don't see the difference between firing these events regardless of the input device (mouse, wacom tablet, finger, etc.) The bigger problem is still that IE is the only browser that uses mouseenter/leave which respond much more appropriately. Mouse events and the box model. Possibly the only two things IE ever had right.