1912358 - Set a proper APZHandledResult in the case of fast-fling

Status: RESOLVED FIXED

(Core :: Panning and Zooming, defect, P2)

Description

[Hiroyuki Ikezoe (:hiro)]

During fast-fling we don't deliver any events to content, but we do scroll the content.

There's a case where we don't properly set APZHandledResult, the case I found is;

1. There's an APZ aware event listener in the content
2. We initialize the APZHandledResult with Nothing()
3. During fast fling the APZHandledResult isn't updated, thus we return Nothing().

I think this is one of the cases that pull-to-refresh is triggered on Uber.com (bug 1903682).

Comment 1

[Hiroyuki Ikezoe (:hiro)]

Attachment: Bug 1912358 - Add a mochitest that any touch event is delivered to content. r?botond

This is for bug 1085404.

Comment 2

[Hiroyuki Ikezoe (:hiro)]

Attachment: Bug 1912358 - Set a proper APZHandledResult in the case of fast-fling. r?botond

During fast-fling, any event isn't delivered to contents, but fast-fling
causes scrolling, thus we need to tell the state to GeckoView via
the APZHandledResult.

The JUnit test case causes an assertion (bug 1852854) without this change.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/1855922d00e0
Add a mochitest that any touch event is delivered to content. r=botond
https://hg.mozilla.org/integration/autoland/rev/373d942b1944
Set a proper APZHandledResult in the case of fast-fling. r=botond,geckoview-reviewers,m_kato

Comment 4

[tszentpeteri]

https://hg.mozilla.org/mozilla-central/rev/1855922d00e0
https://hg.mozilla.org/mozilla-central/rev/373d942b1944