Firefox 116.0 scrolling text up needs 2 swipes every time
Categories
(Core :: Panning and Zooming, defect)
Tracking
()
People
(Reporter: eric.sprik, Unassigned)
Details
User Agent: Mozilla/5.0 (Android 10; Mobile; rv:109.0) Gecko/116.0 Firefox/116.0
Firefox for Android
Steps to reproduce:
Samsung Tab4s tablet with android 10.
Any website.
Actual results:
Recently scrolling gives issues.
Stuttering and scrolling text up only works every 2nd time.
Expected results:
Smooth scrolling as it was before version 116
|
||
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Panning and Zooming' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•2 years ago
|
||
Sounds like this could be related to pull to refresh maybe?
|
||
Comment 3•2 years ago
|
||
Yeah, the "scrolling up only works every 2nd time" symptom sounds very similar to bug 1830805 and bug 1847305.
Eric, could you try disabling pull-to-refresh in the Customize section of Firefox's Settings, and see whether that resolves the issue?
|
||
Comment 4•2 years ago
|
||
Eric, I think pull-to-refresh is disabled by default. Could you try to reproduce this issue again.
|
Reporter | |
Comment 5•2 years ago
|
||
Pull-to-Refresh was OFF.
Enabled it and restarting Firefox did not fix the issue.
On my phone I have Nightly running, without this issue.
|
|
||
Comment 6•2 years ago
|
||
The severity field is not set for this bug.
:botond, could you have a look please?
For more information, please visit BugBot documentation.
|
|
Reporter | |
Comment 7•2 years ago
|
||
Hi.
I notice a relation with Scroll-to-hide-taskbar.
I switched all gesture settings on and off and now its ok with Pull-to-refresh OFF. The Scroll- gesture makes the text move more irratic, not smooth. So, I'm disabling that gesture too.
Possibly there has been a software change with Scroll-to- gesture in new update (?) as I didn't have the problem before. Thx for all the support!
|
|
||
Comment 8•2 years ago
|
||
No problem! Closing for now since things seem to be working, but please feel free to reopen if the issue reappears. Thanks again for opening the bug!
Note: I'm closing this as a duplicate of bug 1830805
Description
•