Bug 97041 - Target can change between GestureTapDown and GestureTap
Summary: Target can change between GestureTapDown and GestureTap
Alias: None
Product: WebKit
Classification: Unclassified
Component: UI Events (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Rick Byers
Depends on: 96677
  Show dependency treegraph
Reported: 2012-09-18 13:41 PDT by Rick Byers
Modified: 2015-08-11 18:11 PDT (History)
3 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Rick Byers 2012-09-18 13:41:05 PDT
The point of GestureTapDown is to provide UI feedback to the user about what they're about to tap on (or already have tapped in some cases).  However, if the page moves (or DOM changes) between TapDown and Tap, we will tap a different element than was highlighted to the user.  Is this OK?  Or perhaps we should do one of:
1) Save the target found for tap down, and re-use it for tap
2) Save the target found for tap down, and do another hit-test on tap but if it doesn't match, dispatch a TapCancel instead

See bug 96677 and http://code.google.com/p/chromium/issues/detail?id=132439 for some more discussion.
Comment 1 Allan Sandfeld Jensen 2012-10-02 07:10:45 PDT
One solution for this is do suspend active DOM objects while the finger is down. This is what I believe the out-of-trunk iPhone and Android branches does, and what Qt does in trunk using Page::suspendActiveDOMObjectsAndAnimations. 

This also has the benefit of smoother animations due to less things happening at the same time.
Comment 2 Rick Byers 2015-08-11 18:11:56 PDT
Haven't really seen issues from this, I don't think we ever did anything to address it in blink either.