Closed Bug 1778186 Opened 3 years ago Closed 2 years ago

Broken scrolling

Categories

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

Firefox 102
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: bigmuscle, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0

Steps to reproduce:

I open some website with longer vertical content with vertical scrollbar.
Same problem appears on my home and work computers regardless the website.

Actual results:

It randomly happens that website starts jumping up and down when scrolling with mouse wheel. This started happening with version 100.

Expected results:

Moving mouse wheel should scroll the website and not randomly jump. It should behave as in pre-100 versions.

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.

Component: Untriaged → Panning and Zooming
Product: Firefox → Core

Thanks for the report. Would you be able to use mozregression to narrow down the window in which the bug was introduced? If you noticed it when upgrading from Firefox 99 to Firefox 100, you can those as the respective start/end points.

Flags: needinfo?(bigmuscle)

Sorry, there was a problem with the detection of inactive users. I'm reverting the change.

Flags: needinfo?(botond) → needinfo?(bigmuscle)

Sounds like the same symptoms of bug 1779404. Given that the original report date is 2022 July 6th (in JST), is it just a coincidence we started seeing a bunch of user's reports related this kind of broken scrolling?

See Also: → 1779404
Severity: -- → S3
Depends on: 1779404
Priority: -- → P3

A needinfo is requested from the reporter, however, the reporter is inactive on Bugzilla. Closing the bug as incomplete.

For more information, please visit BugBot documentation.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Flags: needinfo?(bigmuscle)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.