Fix the case where scrolling_touch_action_ has no value
It seems that TouchActionFilter::scrolling_touch_action_ could have no value in various cases: 1. Start a fling with a touchpad and then do fling boosting with a touch screen. 2. We could have TapDown targeting an iframe and GestureScrollBegin targeting the main frame. This CL does the temporary fix to ensure that the scrolling_touch_action_ always have value. A proper fix with tests will come later. This CL also fixes the case when we try to access the allowed_touch_action_ which could have no value. TBR=creis@chromium.org Bug: 850979 Change-Id: I8dc52a396970d20a7037fa64dc239a25def4fac1 Reviewed-on: https://chromium-review.googlesource.com/1099193Reviewed-by:Xida Chen <xidachen@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#566947}
Showing
Please register or sign in to comment