Closed Bug 1816102 Opened 2 years ago Closed 8 months ago

Pull to refresh activates in Figma

Categories

(Fenix :: General, defect, P2)

All
Android
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: petru, Unassigned)

References

()

Details

Similar to #1815732 but happens more often and to a higher degree. I was even able to trigger pull to refresh while in the middle of the page.
Testing in Fenix I see there are cases in which when we try to sync with GeckoView through InputResultDetail about how the touch was handled we can get multiple times in a row the following the following details here[1] based on which the app will show the pull to refresh throbber:

    inputResult == INPUT_HANDLING_UNKNOWN (-1)
    scrolLDirections == SCROLL_DIRECTIONS_NONE (0)
    overscrollDirections == OVERSCROLL_DIRECTIONS_VERTICAL (2)

Given that this issue depends on fast scrolls I think the issue has more to do with the time APZ needs to infer the touch result.

Video (restricted to Mozilla) - https://drive.google.com/file/d/12VyvIXjWKAF0gyCSMzeJJZxItiabf-SS/view

[1] https://searchfox.org/mozilla-mobile/rev/4c640a0da38ce181ea89e71d20b90a7f881d65b9/firefox-android/android-components/components/concept/engine/src/main/java/mozilla/components/concept/engine/InputResultDetail.kt#258-261

The severity field is not set for this bug.
:cpeterson, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(cpeterson)

S3 since the issue happens on a particular website and depends on fast scroll and so a workaround exists.

Severity: -- → S3
Flags: needinfo?(cpeterson)
Priority: -- → P2

I was not able to reproduce this issue anymore on the latest Fenix Nightly 124.0a1 from 2/2, using a Google Pixel 6 (Android 14).
I'll close this ticket as resolved.

Status: NEW → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.