Closed Bug 283955 Opened 20 years ago Closed 20 years ago

Enable forward/back functionality on compatible mousewheels

Categories

(Camino Graveyard :: General, enhancement)

PowerPC
macOS
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: wtmcgee, Assigned: mikepinkerton)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050226 Camino/0.8+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050226 Camino/0.8+

I currently own a Logitech MX1000 mouse, and one of the features it has is the
ability to use the scroll wheel not only in the traditional way - scrolling up
and down to view content on the page, but it also has the ability to press the
button left and right.  In Firefox on the Mac, this triggers the back/forward
browser functions. This is very helpful, and saves a lot of time when browsing
the web.

Kind of petty, but thought I'd request it be enabled in Camino as well, if
possible.  If this was an intentional move, to allow users to sidescroll when
neeeded, feel free to disregard this request.

Reproducible: Always

Steps to Reproduce:
1.Visit a page, then go to a second.
2.press the scroll button to the left
3.nothng happens

Actual Results:  
Nothing.

Expected Results:  
Left mousewheel should go back, right mousewheel should go forward.
Option+scroll goes through history. Left and right scroll should scroll left and
right from bug 246879
Now, I don't have one of these mice, but it seems to me that if a scroll wheel
is meant for scrolling, we have the correct behavior. In theory, we should (as I
believe LH was saying) allow option scrolling with the left and right movements,
but I think that would be redundant. I suggest WONTFIX.
Given the bug mentioned in comment 1, I'd also say WONTFIX.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
If you *really* want horizontal scroll to move through the history, you can
probably tweak the prefs mentioned in bug 246879 in your user.js file.
You need to log in before you can comment on or make changes to this bug.