Scrolling up only works every other attempt on some pages (i.e. Google, Github, about:config)
Categories
(Fenix :: Browser Engine, defect)
Tracking
(firefox119 affected)
Tracking | Status | |
---|---|---|
firefox119 | --- | affected |
People
(Reporter: accounts.mozilla, Unassigned)
Details
(Whiteboard: [qa-triaged])
Attachments
(1 file)
759.72 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/117.0
Steps to reproduce:
- Navigate to one of the affected sites. For example: https://google.com/search?q=firefox or https://github.com/mozilla-mobile.
- Scroll to the bottom.
- Attempt to scroll up.
Actual results:
Scrolling up only works every other attempt.
Screen recordings:
- Google: https://www.youtube.com/watch?v=gN31-r97YLM
- Github: https://www.youtube.com/watch?v=Sh38Trx-cpw
Expected results:
Scrolling up should work every attempt.
Reporter | ||
Comment 1•1 year ago
|
||
I've tested this in 117.1.0 and nightly (119.0a1, Build #2015973955, 418fb80f34) and they both exhibit the same behavior.
From a user perspective, the symptoms seem similar to https://bugzilla.mozilla.org/show_bug.cgi?id=1724755, but I don't know if it's the same root cause, so I filed a new bug report (and the linked bug report is for a specific site anyway).
Reporter | ||
Comment 2•1 year ago
|
||
I just noticed this happens with the builtin about:config
page too.
Comment 3•1 year ago
|
||
I was able to reproduce this behavior only on about:config page on the latest Nightly 119.0a1 from 9/18 with Google Pixel 6 (Android 14), and HTC 10 (Android 8).
Not able to reproduce on the pages mentioned in the initial description.
Comment 4•1 year ago
|
||
Reporter | ||
Comment 5•1 year ago
|
||
This seems to be fixed by https://bugzilla.mozilla.org/show_bug.cgi?id=1847305. None of the pages where I encountered this before exhibit the issue anymore after those commits were introduced.
Comment 6•5 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Fenix::Browser Engine' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Description
•