Closed
Bug 303913
Opened 19 years ago
Closed 18 years ago
[Firefox 1.0.x branch] Support horizontal scrolling with Mighty Mouse properly
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: manfred, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; de-DE; rv:1.7.10) Gecko/20050717 Firefox/1.0.6 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; de-DE; rv:1.7.10) Gecko/20050717 Firefox/1.0.6 Please support the horizontal scrolling with the Mighty Mouse properly. Reproducible: Always Steps to Reproduce: 1. Browse a long web page (which does not! need horizontal scrolling) 2. Scroll vertical with the Mighty Mouse Actual Results: The Mighty Mouse has a ball. If you scroll vertically but do not perfectly do so and just a little bit scroll horizontally, Firefox jumps back a few pages. Expected Results: Scrolling vertically with the Mighty Mouse should scroll vertically, and horizontally should scroll horizontally with that mouse. It should not go pages back and forward. Every other application uses the horizontal scroll feature of the Mighty Mouse to scroll a document horizontally. Firefox should do so as well. The page jumping feature is totally unexpected and confusing. Also the page jumping is very annoying since it is very easy to accidently jump pages when using the ball of the Mighty Mouse. Firefox should not do that. It makes the scrollball of the Mighty Mouse unusable in Firefox.
Comment 1•19 years ago
|
||
Already fixed on trunk (see bug 231718 and bug 303537). Morphing this bug slightly so it's for backporting that fix to the 1.0.x branch. This bug is suddenly more visible because of Apple's release of the Mighty Mouse, so it might make sense to backport the fix for bug 231718 to the 1.0.x branch.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking-aviary1.0.7?
Summary: Support horizontal scrolling with Mighty Mouse properly → [Firefox 1.0.x branch] Support horizontal scrolling with Mighty Mouse properly
I think this problem lies a little deeper then that patch. I'm running the latest (its a day or 2 old), with my Mighty Mouse on Linux. The problem isn't that there is no scrolling, it is actually related to an incorrect mapping of the buttons. On virtually all Linux apps (and I would imagine this is the case for OSX), buttons 6/7 are mapped to scroll sideways. Yet, under firefox, theyre mapped to forward/back. Most people right now dont have the buttons, and it probably works just fine, however, I wouldn't mind seeing a config option to change this, even if it is obscured in about:config. That way, people running Firefox without the scrolling, can continue to do so without modifying their xmodmap, while users who have scrolling, and would really love to use it, can also use it in a way that doesn't interfere with their other side-scrolling enabled applications. Perhaps something like mousewheel.horizscroll.complaince of a bool. I have no idea how I would go about coding such a fix, and if I did, it would be a terrible hack that would never be accepted, but I'm sure theres enough skilled coders out there who would love to see this changed.
Maybe I'll clarify. there is the mousewheel.horizscroll.withnokey.action (and its variant modifiers), but I would still like my forward and back to work. Remapping the forward and back to 8/9 would be benificial. I suppose instead adding an option for mouse forward/back keys would be benificial. Perhaps I'm not every good at looking, but I cant seem to find an option to use mouse buttons 8 and 9 to back/forward.
Comment 4•19 years ago
|
||
*** Bug 315291 has been marked as a duplicate of this bug. ***
Comment 5•19 years ago
|
||
no patch, not a security problem: not blocking 1.0x
Flags: blocking-aviary1.0.8? → blocking-aviary1.0.8-
Comment 6•19 years ago
|
||
There's a small patch on bug 231718 that can probably be ported to Firefox 1.0.x without much trouble. Might not be worth it, though; this bug has surprisingly few dups.
Comment 7•18 years ago
|
||
The 1.0.x codebase has been retired and there will be no more releases from this branch.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•