1813208 - [Bug]: If a nested scroll area is scrolled to the bottom, scrolling up triggers "pull to refresh"

Status: RESOLVED WORKSFORME

(Firefox for Android :: Toolbar, defect)

Description

[Jonathan Almeida [:jonalmeida]]

From github: https://github.com/mozilla-mobile/fenix/issues/21405.

Steps to reproduce

• Visit https://tasvideos.mistflux.net/ on Firefox Fenix and close the gray message. If this URL goes down in the future, visit my archived copy.
• Ensure you are scrolled to the very top of the page.
• Swipe up on any of the scrollable areas to scroll to the very bottom of the area. (If you're scrolled partway down, the bug doesn't happen.)
• Swipe down on the draggable areas to drag it down.

Expected behaviour

The draggable area should move down.

Actual behaviour

Firefox triggers a "pull to refresh" action.

If you drag sideways then down, the scrollable area scrolls down for a bit, then triggers a "pull to refresh". A second drag doesn't trigger the bug because the scroll area is no longer scrolled to the very bottom.

Device name

Google Pixel 4a

Android version

Android 11

Firefox release type

Firefox Nightly

Firefox version

94.0a1 (Build #2015835243)

Device logs

No response

Additional information

Possibly related to #16089.

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

Comment 1

[eclaudiu64]

I also noticed this error on Youtube's desktop site. It's still on the latest versions of Firefox Nightly, Firefox Beta, and Firefox Stable. When will this error be resolved?

Comment 2

[Mira Lobontiu (Android QA)]

I was not able to reproduce this issue on the https://tasvideos.mistflux.net/, neither on the youtube.com on desktop mode.
Tested on the latest Fenix Nightly 114.0a1 from 4/20 with Xiaomi Mi8 Lite (Android 10).

Claudiu, could you, please, provide us the devices you've encountered this issue on, and maybe a short video?
Thank you!

Comment 3

[eclaudiu64]

Attachment: mobizen_20230420_183929_001_001_001.mp4

I tested on the phone model Samsung A20E, Moto E7 Plus. It automatically pulls to refresh while pulling up the list from youtube desktop. I also reset the phone and the same thing happens.

Comment 4

[eclaudiu64]

Attachment: mobizen_20230420_191223.mp4

And on the website https://nyanpasu64.github.io/tasvideos.mistflux.net . In the first frame you can see that you can't scroll up that list, because pull to refresh is triggered. In the Chrome browser it works and pull to refresh does not trigger.

Comment 5

[Lorand Janos]

I've managed to reproduce the described issue using the archived copy of https://tasvideos.mistflux.net/.
Once I scrolled to the bottom of the framed part from the top of the page, I can only activate pull to refresh instead of scrolling back up. The content from the second frame has the same behavior on scroll (as long as the main page remains in the top view). Workaround would be to interact with the rest of the page, scrolling down on it a bit faster, than returning to the top of the page, and not
Tested on the latest Nightly 114.0a1 (2023-04-20) build.
Device used: Google Pixel 7 (Android 13).

Comment 6

[Botond Ballo [:botond]]

The issue depicted in comment 3 (which does not involve a nested scroll area) looks like the one tracked in bug 1724755 and related bugs (the ones listed in its "See Also" field).

The issue on https://tasvideos.mistflux.net/ may also be the same issue, but it needs further analysis to rule out issues related to the nested scroll area.

Comment 7

[Botond Ballo [:botond]]

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

The issue on https://tasvideos.mistflux.net/ may also be the same issue, but it needs further analysis to rule out issues related to the nested scroll area.

I was able to reproduce this on the archived version of the site at https://nyanpasu64.github.io/tasvideos.mistflux.net/. I investigated this a bit, and confirmed that APZ is sending the expected InputResult values, so this is a bug on the application side.

Interestingly, in the scenario where the unexpected pull-to-refresh happens, APZ sends an eager InputResult value of HANDLED, suggesting that the bug on the application side is a different one than bug 1724755 (which affects scenarios with delayed InputResult values).

Comment 8

[Mira Lobontiu (Android QA)]

I was not able to reproduce this issue anymore on Fenix Nightly 124.0a1 builds from 1/31, and 2/1.
Tested with the following devices:

• Google Pixel 6 (Android 14),
• Lenovo tablet M10 (Android 10), and
• Samsung Galaxy A14 (Android 13).

I'll close this ticket as Worksforme.