using Scroll Wheel in Firefox 3.6 Beta 2 scrolls up faster than down

RESOLVED INCOMPLETE

Status

()

Firefox
General
--
major
RESOLVED INCOMPLETE
9 years ago
8 years ago

People

(Reporter: Bryan Reynolds, Unassigned)

Tracking

3.6 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2b2) Gecko/20091108 Firefox/3.6b2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2b2) Gecko/20091108 Firefox/3.6b2

After upgrading to Firefox 3.6 Beta 2 today I noticed that using the mouse wheel to scroll up seems to move the page about double what scrolling down does. Earlier today in 3.6 Beta 1 I did not have this problem.

I'm using a Logitech G9 Laser mouse on Windows 7 64bit with the latest SetPoint installed (5.20.40). I've tried deleted and re-recreating my mouse settings, starting/stopping the setpoint service, unplugging/replugging my mouse.

The issue isn't occurring in other programs like Chrome or IE8, only Firefox.

Reproducible: Always

Steps to Reproduce:
1. navigate to any website where you can liberally scroll up and down with the mouse wheel
2. scroll DOWN a few times, then scroll UP, notice that scrolling up moves the page up a lot further. They should move equal distance both ways.
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2b3pre) Gecko/20091110 Namoroka/3.6b3pre

This seems true, but I see the same with all browsers.
My guess is that this is due to the way people use their finger muscles.
Version: unspecified → 3.6 Branch
Maybe Alex Faaborg can confirm or deny this.
Also CC-ing Kyle Huey who it a mouse person if I remember well.
any chance bug 513817 caused this?
Bryan:

Can you reproduce this problem after you change mousewheel.system_scroll_override_on_root_content.enabled to false in about:config?

If so, this is a regression of bug 513817.
(In reply to comment #5)
> If so, this is a regression of bug 513817.

er, If *not* so...
there is no reply from the reporter and nobody can reproduce this bug...
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
probably, this is same as bug 543511 which was fixed on trunk.
You need to log in before you can comment on or make changes to this bug.