Issue metadata
Sign in to add a comment
|
Touch-action pinch-zoom is determined on touchstart |
||||||||||||||||||||||||
Issue descriptionThere is an interop issue with respect to pinch-zoom between Edge and Chrome. In Edge: Have a page that has touch-action: pinch-zoom Place one finger on the page and drag notice it doesn't drag. Put another finger down on the page to pinch-zoom. Notice you can drag with both fingers. In Chrome: Once you start a gesture placing fingers more fingers down doesn't change the initial gesture. So pinch zoom and panning aren't permitted. We need to determine when the touch-action filter should be determining this. Currently we took the easy way and did it in the first GestureScrollBegin. A GesturePinchBegin/End is always wrapped by a GestureScrollBegin/End. If this was done inside the GesturePinchBegin then we would break the contract of the GPB/GPE being wrapped by a GSB/GSE.
,
Dec 9 2016
,
Jan 5 2017
Any idea which part of Chrome relies on GPB/GPE being bracketed by GSB/GSE?
,
Feb 23 2017
Seems we can't rely on GPB directly: Issue 632525 implies that a 2-finger drag should be treated like a pinch-zoom but on Android a two finger drag doesn't fire a GPB until the distance between the fingers changes by some delta. E.g. for a nearly parallel 2-finger drag, there are no GPB/GPE events. Perhaps we can change the definition of a gesture-pinch to include any 2-finger gesture so that there will be a GPB at the moment any finger in a multi-finger gesture moves. Not sure how it would affect assumptions in other parts of Chrome.
,
Mar 9 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. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 15 2018
Still an issue in 2018 Q1 check-in.
,
Nov 19
Assigning xidachen@ who is working on touch-action related things.
,
Nov 19
I believe this is fixed, the root cause is the same as crbug.com/771330
,
Nov 19
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Sep 21 2016