1686147 - Fling animation blocks completion/reset of overscroll animation

Status: NEW

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

Description

[Sawyer Bergeron]

Steps to reproduce:

1. Begin an X axis overscroll and hold view in overscrolled state
2. Begin a Y axis fling

Observed results:
View remains overscrolled while fling animation completes. Overscroll only resets once fling animation completes.

Expected results:
View completes overscroll animation concurrently with fling animation, or overscroll is instantaneously reset before fling animation is allowed to begin

Comment 1

[Botond Ballo [:botond]]

Markus has a (likely somewhat bitrotted) patch for this here.

Comment 2

[Timothy Nikkel (:tnikkel)]

When I test I get the observed results in Safari, and the expected results in Chrome.

Comment 3

[Botond Ballo [:botond]]

(In reply to Timothy Nikkel (:tnikkel) from comment #2)

When I test I get the observed results in Safari, and the expected results in Chrome.

Markus, does this match what you see? (If so, can we downgrade this from blocking the initial release of overscroll?)

Comment 4

[Markus Stange [:mstange]]

I can confirm that Safari has the "observed results". Weird! Ok, then I guess we can downgrade this.

Comment 5

[Botond Ballo [:botond]]

Here is a good test page for this issue (STR: overscroll to the left and then fling downward without releasing the touchpad in between). I find that on shorter pages the fling reaches the end of the page pretty quickly, making the issue harder to notice.

Comment 6

[Botond Ballo [:botond]]

I think this may be fixed by bug 1700215?

Comment 7

[Botond Ballo [:botond]]

(In reply to Botond Ballo [:botond] from comment #6)

I think this may be fixed by bug 1700215?

Bug 1700215 fixed this issue for Mac but not for Linux (where flings have a different implementation). We'll keep this open to track the Linux issue.

Comment 8

[Botond Ballo [:botond]]

Just a heads up, per bug 1752246 comment 3, we are planning to enable overscroll on Linux by default in Firefox 130.

We have not received other reports of this issue so we are not considering this a blocker for that enablement. However, we'd still like to fix this at some point, and will keep the ticket open.