Fling tap suppression should be per scroller. |
|||||
Issue descriptionCurrently, if you fling a subscroller, and then tap something outside of the subscroller, we still suppress the tap and cancel the fling. There's no good reason to cancel the tap in this context. We haven't received any complaints about this, so it's pretty low priority.
,
Mar 16 2017
,
Apr 16 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 27 2018
This is still currently true but I think it'd be hard to do in our current architecture. The tap suppression happens in the browser so we'd have to do a round trip to the renderer to determine if the tap would be inside the current scroller or not. Sahel, can you confirm if that's the case?
,
Apr 30 2018
Yes it is still the case, but I don't think it an issue since the user still sees some changes in response to the tap (fling being cancelled).
,
May 9 2018
Yeah, I think Tim's thought was we shouldn't cancel the fling (since you tapped on something that wasn't scrolling) and issue a tap instead. Given the complexity - benefit tradeoff today I don't think it's worth pursuing. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by sheriffbot@chromium.org
, Mar 16 2017Status: Untriaged (was: Available)