Bug 1847305 - Re-initialize inputResultDetail at the right time.
commit6c7bb7a8d26f56729b129814b55d33020d5c94f7
authorHiroyuki Ikezoe <hiroyuki.ikezoe@gmail.com>
Tue, 12 Sep 2023 00:32:32 +0000 (12 09:32 +0900)
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Thu, 7 Dec 2023 10:41:53 +0000 (7 10:41 +0000)
tree77c098f66d249cfc0fe9d53c696f0a9345c28f8e
parent43be6442ae7d32bafcaea3087a073422b37b8b19
Bug 1847305 - Re-initialize inputResultDetail at the right time.

And invoke requestDisallowInterceptTouchEvent just before sending a new
ACTION_DOWN and invoke it againg just after receiving the result from
Gecko so that we can properly hold off triggering pull-to-refresh.

Re-initializing inputResultDetail on ACTION_UP or ACTION_CANCEL is
problematic since Gecko sends the result asynchronously thus it's
possible that Gecko sends the result after re-initialization on
ACTION_CANCEL.

Co-authored-by: Titouan Thibaud <tthibaud@mozilla.com>
mobile/android/android-components/components/browser/engine-gecko/src/main/java/mozilla/components/browser/engine/gecko/NestedGeckoView.kt