Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1248939 - Scrolling down in Firefox leads to FAST scrolling down
Summary: Scrolling down in Firefox leads to FAST scrolling down
Keywords:
Status: CLOSED DUPLICATE of bug 1245247
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk3
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-31 07:48 UTC by Fabian Deutsch
Modified: 2015-08-03 07:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-03 05:42:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Fabian Deutsch 2015-07-31 07:48:20 UTC
Description of problem:
Quite often when scrolling down in (at least a Firefox page) results in teh page scrolling down VERY FAST the first time when I use the mouse wheel.
The second or third time I use the mouse wheel to scroll down (in the same "process") all works as usual. This is a very annoying bug, I'm not sure if it's FF or libinput.

reddit thread:
http://www.reddit.com/r/Fedora/comments/3dyj38/sometimes_really_fast_scrolling_after_upgrade_to/

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Open a longer webpage in Firefox on F22 (XOrg)
2. Scroll down using the mouse wheel
3. 

Actual results:
The first time the scroll wheel is turned the page nearly jumps downards

Expected results:


Additional info:

Comment 1 Peter Hutterer 2015-08-03 05:42:43 UTC

*** This bug has been marked as a duplicate of bug 1245247 ***


Note You need to log in before you can comment on or make changes to this bug.