Safari scrolling is slower, and we saw similar behavior, but it wasn't as noticeable since there wasn't as much scroll momentum.

If I go to espn.com on safari, scroll, and immediately tap somewhere while the page is scrolling, safari navigates (this is on an iphone 6s, 9.3).

Safari's momentum is reduced compared to Chrome, so 'flings' last longer on Chrome as compared to Safari.  However, I'm seeing the same functionality, between the two.

Am I misunderstanding here?   Or maybe did 9.3 change something?

Justin, I think you're understanding the issue that reported correctly.  Maybe it really is a momentum thing and not a difference in deciding what to do about taps.

I am not sure if 9.3 changed anything.

Should we mark this WontFix ?

> Should we mark this WontFix ?

I don't think we should dismiss this issue so out of hand.  This is a sophisticated user who tells me that this regularly drives him back to Safari.

Can we at least collect some metrics that indicate how often we have a tap in a situation of low momentum and in a situation where we believe Safari would've had no momentum?

I suggested WontFix because I cannot reproduce the problem, on iPad or iPhone.  If I tap-to-stop-scroll on Chrome on iOS 9.3, it doesn't trigger a navigation, it stops the scroll.

mpearson@ can you provide more details on what version of Chrome, device type, os version, the users is running?

Thanks!

I'll get you the info you need.

justincohen@, you are trying this on espn.com in particular?  He said he doesn't have this problem (much?) on other web sites.

iPhone 6
iOS 9.3 (13E233)
Chrome 49.0.2623.109

Every time I fling and tap on safari it opens a new tab.  Am I on the wrong site?

Deleted: Fling and Tap.mov 11.0 MB

Fling and Tap.mov 11.0 MB Download

blink is not on iOS removing its components

> Every time I fling and tap on safari it opens a new tab.  Am I on the wrong site?

Looks like the right site to me.  I think you are seeing the behavior the user is complaining about.  The user wants tapping to start a scroll (possibly while the page is still scrolling) not to open anything, simply stop scrolling and start another scroll.

I'll try to be clearer about what I observed:
I think what the use is doing is putting a finger on the touchscreen, flinging it slightly, putting a finger down, flinging it slightly, and so on, almost like gently petting the touchscreen with half-inch-long strokes.  Often these putting the finger down actions cause a navigation.  In Safari he says he doesn't have this problem.  Maybe there's a difference (on this site in particular?) with when taps are recognized as starting a scroll versus a request to navigate?

mpearson@ does this video help?  The first app is Chrome, with a relatively fast 'putting finger down and fling again' vs a slow 'putting finger down and fling again'.  On the second, sometimes the context menu pops, but never a redirect.

The second app is safar, with a slower fling (by design) and a longer tap to context menu, by design, but basically the same functionality.  

Or am I completely misunderstanding this bug!

Deleted: Fling and Tap Video 480p.mov 23.5 MB

Fling and Tap Video 480p.mov 23.5 MB Download

Thank you, everyone, for investigating! (I'm the original Chrome user who had the problem...)

There's a subtle difference between "tap to stop scrolling" and "tap and *hold* to stop scrolling." The latter works fine, but the former causes a page to open on ESPN.  

I've attached a video of the issue, in case it helps.

It did occur to me that some users might want tap-and-release to click on a target, not just stop scrolling. But for me at least, that is never the intended behavior. (And on all other sites I have tried, tapping and releasing just stops scrolling - it won't open any page.)

For whatever subconscious, muscle-memory reasons, this is how I scroll, so it's hard for me to change my behavior. I wonder how many others might have this problem.

Deleted: VID_20160417_121136.mp4 12.1 MB

VID_20160417_121136.mp4 12.1 MB Download

I am manual sheriffbot.  Thank you for providing more feedback. Adding requester "justincohen@chromium.org" for another review and adding "Needs-Review" label for tracking.

dakers@ comment #9 is safari 'tap to stop scrolling', and it cause a page to open -- e.g. Safari is also doing what comment #15 is describing.

David, do you think you can eugenebut@ explain this one in person?

Claude, could you please ask QA to compare behavior of Safari, Firefox, Chrome and WebView app.

My understanding from an offline thread with Eugene and Justin is that this is out of Chrome's control ('working as apple intends' with WKWebView). Behavior of Safari and Chrome at least should be consistent - it's just that Chrome's momentum scrolling makes it easier for this problem to affect people (since scrolling continues for longer after a swipe, so it's more likely for people to tap while scrolling is still occurring). So the only "fix" might be to reduce the momentum in momentum scrolling for Chrome - but it sure is nice for other reasons...

Tested on 52.0.2743.49 dev, iPad iOS9.3.2
This issue is reproducible in safari, firefox and chrome. When scrolling the page and tap on any link, the page opens.

dakers@ I think we can close this as WontFix, but please let me know if there's something we missed that's still fixable.

Thanks-

If there were a way to disable tapping to open links during scroll, I would say that would be beneficial (at least to me!) - but it does sound like this behavior is consistent across browsers, and working as intended from Apple's perspective. I'm OK with marking this as wont-fix.