Closed Bug 282575 Opened 21 years ago Closed 21 years ago

Logitech Setpoint software back and forward defaults do not work

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 259450

People

(Reporter: mikecp, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050210 Firefox/0.10 StumbleUpon/1.998 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050210 Firefox/0.10 StumbleUpon/1.998 The new MX 1000 Logitech mouse comes with its driver/software known as setpoint. It defaults mouse4 and mouse5 (the side thumb buttons on most mx mice) to back and forward respectively. However, the back and forward only work on Internet Explorer and the user is forced to assign mouse4 and mouse5 to the keystroke alt+left arrow and alt+right arrow. Somewhat of an inconvenience (especially for gamers that like to bind actions ingame to those buttons) for the user in-the-know. More importantly, the average user will not know how to use this workaround. Reproducible: Always Steps to Reproduce: 1.Plug in MX 1000 mouse. 2.Install Setpoint software and reboot as directed 3.Open Firefox, find that mouse4 and mouse5 do not navigate back and forward Actual Results: I got frustrated and did a workaround in the setpoint software to assign those keys to the back and forward key stroke of firefox Expected Results: set to back and forward by default, the mouse should click navigate correctly in firefox I'm hesitant to call this a minor bug because non-techie users of this mouse software would probably not know the workaround
Please search before you file a bug. The problem is the mousedriver and not Mozilla. *** This bug has been marked as a duplicate of 259450 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.