User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b5) Gecko/2008032619 Firefox/3.0b5 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b5) Gecko/2008032619 Firefox/3.0b5 After installation of Firefox 3 RC1, autoscrolling and mouse scrolling fuctions with Apple Mighty Mouse were disabled. Previously, both worked. Attempts to remedy via unchecking and rechecking these functions in the FFox preferences and restarting FF were unsuccessful. Am able to scroll only by use of the down/up arrow buttons on the FF page. Reproducible: Always Steps to Reproduce: 1. Start FF RC1 and attempt to scroll with Apple Mighty Mouse. 2. 3. Actual Results: No scrolling possible. Expected Results: Scrolling should occur.
I can't reproduce this. > Attempts to remedy via unchecking and rechecking these functions in > the FFox preferences and restarting FF were unsuccessful. Which Firefox preferences, exactly? You should also check the Keyboard & Mouse pref panel (in System Preferences) to make sure Scrolling hasn't been set to "Off". The default value for Scrolling is "Vertical and Horizontal". If you haven't got this set to "Off", is it set to something else besides "Vertical and Horizontal"?
This is a mass search for bugs that are in the Firefox General component, are UNCO, and have not been changed for 800 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the bug, please update this bug. If the issue is gone, please set the resolution to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.