Closed Bug 1731840 Opened 4 years ago Closed 4 years ago

[Bug]: Scrolling of Flutter 2.x apps does not work but works fine in Google Chrome and in the desktop version of Firefox

Categories

(Core :: Panning and Zooming, defect)

Unspecified
Android
defect

Tracking

()

RESOLVED DUPLICATE of bug 1725416

People

(Reporter: kbrosnan, Unassigned)

References

Details

(Whiteboard: [apz-android-needstriage])

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

Steps to reproduce

Open https://flutterlistview.netlify.app/ and try to scroll the page. It cannot be scrolled (only very slow in very small steps and it stops after each scroll gesture) in Firefox on Android but in works fine in Firefox on macOS and Google Chrome on Android.

There is also a bug report for Flutter here:

https://github.com/flutter/flutter/issues/88358

But I thought I should also post it here because is might be a bug in Firefox for Android, not a bug in Flutter, if it works fine in Firefox for macOS and Google Chrome.

Expected behaviour

The page should be scrollable.

Actual behaviour

It cannot be scrolled (only very slow in very small steps and it stops after each scroll gesture).

Device name

Google Pixel 2 XL

Android version

Android 11

Firefox release type

Firefox

Firefox version

91.4.0

Device logs

No response

Additional information

No response

Change performed by the Move to Bugzilla add-on.

Whiteboard: [apz-android-needstriage]

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

For more information, please visit auto_nag documentation.

Flags: needinfo?(botond)

Marking as S2 for an issue that potentially prevents users from scrolling sites using this framework on mobile.

I had a brief look at the page but it's very hard to understand what the event handlers are doing due to the JS being minified. I asked in the corresponding Flutter issue if an example with non-minified JS can be provided.

Severity: -- → S2
Flags: needinfo?(botond)

Per discussion in Flutter issue, the issue is no longer present in Firefox 93.

I got a fix range, looks like it was fixed by bug 1725416.

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