Remove TouchActionFilter::num_of_active_touches_
This variable was added to test whether the touch start / end can be acked and released out of order or not. From the reading of the code, I don't think is true. This CL removes this variable, we will monitor crash reports to ensure this doesn't cause regression. To ensure the same behavior, we need a new variable, which is named |touch_sequence_in_progress_| in this CL. This is specifically for this scenario: we have received touch event ack for touch start, and then JS removes / adds touch event listener, which triggers a OnHasTouchEventHandlers call. In this case, we should not reset touch action if the |touch_sequence_in_pgoress_| is true. We have the unit test OnHasTouchEventHandlersReceivedAfterTouchStart to ensure this behavior. Bug: 900195 Change-Id: I53c3141905b4e2a49ab6e62ea43335c4cee17c15 Reviewed-on: https://chromium-review.googlesource.com/c/1307250 Commit-Queue: Xida Chen <xidachen@chromium.org> Reviewed-by:Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#604260}
Showing
This diff is collapsed.
Please register or sign in to comment