1903682 - Stuck scrolling and unintended pull-to-refresh in Uber web app in past rides list

Status: RESOLVED FIXED

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

Description

[Markus Stange [:mstange]]

Steps to reproduce:

1. Go to https://m.uber.com/
2. Log in with your Uber account.
3. Open the sidebar with the hamburger button in the top right.
4. Tap on "My Trips".
5. Scroll down to the "Past" section and to the bottom of the list of your past trips (the list has four entries for me).
6. Try to scroll back up.

Expected results:
You should be able to scroll up normally.

Actual results:
On the first try, scrolling gets stuck after a few pixels and the scroll gesture turns into a pull-to-refresh gesture. If you don't stop moving your finger fast enough, the page refreshes. Luckily there's no data loss and you stay on this page.
After the first stuck scroll, the second scroll up works.

I'm not going to attach a screen recording of this because the list contains my address.

Comment 1

[Markus Stange [:mstange]]

Chrome does not get stuck scrolling this list, and it does not engage pull-to-refresh.
In Chrome I can get stuck if I attempt to scroll the list further down (but it's already at the bottom), and, without lifting my finger, then scroll up during the same gesture. This scrolls the outer page and doesn't get very far.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

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

For more information, please visit BugBot documentation.

Comment 3

[Hiroyuki Ikezoe (:hiro)]

Creating a uber account requires a phone number so I am not going to test this bug.

The symptoms in comment 0 sounds like it might be fixed by the patch for bug 1897567, I hope.

Comment 4

[Botond Ballo [:botond]]

Markus confirmed that:

• Bug 1902313 did not fix this
• The patch for bug 1897567 (which I pushed to Try here) partially fixes this. However, the issue can still be reproduced intermittently if you fling to the bottom and then try to scroll up.

Comment 5

[Hiroyuki Ikezoe (:hiro)]

(In reply to Botond Ballo [:botond] [away until Aug 12] from comment #4)

• The patch for bug 1897567 (which I pushed to Try here) partially fixes this. However, the issue can still be reproduced intermittently if you fling to the bottom and then try to scroll up.

My hypothesis is that it happens with nsEventStatus_eConsumeNoDefault during fast fling.

I commented the scenario somewhere else but I couldn't find it now. Right after the time I commented it, I thought the scenario should not happen on Android since I believed fling is specific to Linux, then Botond corrected me that fling also happens on Android.

I am mostly 100% sure the assertion (bug 1852854) should have happened on debug builds.

Comment 6

[Markus Stange [:mstange]]

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

• The patch for bug 1897567 (which I pushed to Try here) partially fixes this. However, the issue can still be reproduced intermittently if you fling to the bottom and then try to scroll up.

This is still happening: When I fling down and then scroll up, I still get stuck in pull-to-refresh. This is with the Nightly build from the Play Store which contains a Gecko view from August 28.

Comment 7

[Botond Ballo [:botond]]

Markus confirmed that the patch for bug 1916897 does fix the remaining issue!

Comment 8

[Hiroyuki Ikezoe (:hiro)]

As per comment 7 and a new nightly version including the patch for bug 1916897 has been rolled out via Google Play Store, I am going to close this bug.

The nightly revision on my end is 50016ed27344.