Revert "Set touch action Auto in MaybeSendSyntheticTapGesture"
This reverts commit ec552f22. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 583369 as the culprit for flakes in the build cycles as shown on: https://findit-for-me.appspot.com/waterfall/flake/flake-culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vZWM1NTJmMjI5NTM5NzM4NzFjZWExZTYyNWNmNmIzNjZjOGMzNjM0NQw Sample Failed Build: https://ci.chromium.org/buildbot/tryserver.chromium.chromiumos/linux-chromeos-rel/71344 Sample Failed Step: mash_browser_tests (with patch) Sample Flaky Test: ChromeSitePerProcessPDFTest.SendSyntheticTapGestureOOPIF Original change's description: > Set touch action Auto in MaybeSendSyntheticTapGesture > > The MaybeSendSyntheticTapGesture can be called in PreProcessMouseEvent, > in which case the TouchActionFilter::allowed_touch_action_ has no value > and will result in a crash. > > This CL set the allowed_touch_action_ to auto to fix the issue. A > browser test is added. > > Bug: 873211 > Change-Id: If776a93fe2c8f7a311a10bc0fec42cda15d0ae9a > Reviewed-on: https://chromium-review.googlesource.com/1169585 > Commit-Queue: Xida Chen <xidachen@chromium.org> > Reviewed-by: Alex Moshchuk <alexmos@chromium.org> > Reviewed-by: Timothy Dresser <tdresser@chromium.org> > Cr-Commit-Position: refs/heads/master@{#583369} Change-Id: I2b4c4fb6b76a7a904603e7bf1086fe4f42d9f1e3 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 873211, 874667 Reviewed-on: https://chromium-review.googlesource.com/1176503 Cr-Commit-Position: refs/heads/master@{#583438}
Showing
Please register or sign in to comment