Do not set touch action to Auto at GSB if it is already set
In chrome VR or virtual keyboard case, we can get GestureScrollBegin without GestureTapDown, and that |scrolling_touch_action_| may have no value. In this case, we set it to Auto to prevent crash. This was done in a previous CL: https://chromium-review.googlesource.com/c/chromium/src/+/1195649 However, there was a small mistake in the previous CL. That is, the |scrolling_touch_action_| could have been set when the browser receives the ACK for the touch start from the main thread. In this case, we should not set it to Auto. Bug: 880701 Change-Id: I250bb7a09840f16665cfcf5826236cad99b533c5 Reviewed-on: https://chromium-review.googlesource.com/1213502Reviewed-by:Navid Zolghadr <nzolghadr@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#590059}
Showing
Please register or sign in to comment