mouse "cruise" scrolling buttons work erratically after upgrade to ff 1.0.1




Shell Integration
13 years ago
12 years ago


(Reporter: Chris Sokol, Assigned: Ben Goodger (use ben at mozilla dot org for email))


Firefox Tracking Flags

(Not tracked)




13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

I have a logitech mx 500 mouse, which has buttons above and below the scroll
wheel which can (and have) been assigned to "cruise" - they act like i'm
scrolling the wheel.  They worked fine in ff 1.0, and they continue to work fine
in other apps.  After upgrading to ff 1.0.1, they only work occasionally.  it
seems like some internal state thing, rather than a page related issue: i
searched for the bug in bugzilla, and was able to navigate the page with the
cruise buttons.  i then switched to outlook webmail, which i had in another tab.
 the cruise buttons did not work there, and when i switched back to the bugzilla
tab, they would no longer work there.

Reproducible: Always

Steps to Reproduce:
1. Configure a logitech mouse with cruise buttons
2. Open a page which is tall enough to need scrolling
3. Try and scroll with the cruise buttons
4. If it works, surf around a bit and return to 3.

Comment 1

13 years ago
i have noticed that if another application has focus, and in front of ff, when i
hover over ff and use the cruise buttons, they work reliably.  when i switch
focus to ff, they stop working.  switch back to the other app, cruise works
again, etc.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.