FastClick clicks on incorrect element if using iOS 6 and an active CSS transition or scroll fling

[rowanbeentje]

iOS 6 appears to have introduced a bug where the event.target element for input events is incorrect if the input was within an area that is being actively scrolled or CSS transformed. The event.target supplied by the browser isn't the element targeted by the input event; instead, it is the element that was at that position before the scroll/transition started.

This means that FastClick currently can click an element other than the intended element if it is within a parent that is being transitioned or is being scrolled.

(This is the underlying cause of Issue #42, although it may still be desirable not to send clicks when an element is scrolling.)

Further investigation seems to find that document.elementFromPoint can be used as a workaround as it gives the correct coordinates, but only reliably if it is called after event.targetElement, which seems to trigger an update of some kind after it's used. I've put a reduced testcase showing the odd behaviour up at http://beent.je/ios-targetelement-bug.html .

(Appears to still be present in iOS 6.1b4, so reported to Apple as rdar://13048589 )

[CristyTarantino]

Hi, I still have this problem when I save the page as home Screen App on my IOS devices.