Closed Bug 93158 Opened 24 years ago Closed 23 years ago

Internet mouse buttons do not fuction under Windows ME

Categories

(SeaMonkey :: General, defect)

x86
Windows ME
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 30431

People

(Reporter: mephiska, Assigned: mpt)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98; Win 9x 4.90) BuildID: 2001062815 The internet mouse button actions "Back", "Forward" and "AutoScroll" do not work with Mozilla under Windows ME. They do, however, appear to work with Windows 2000. Reproducible: Always Steps to Reproduce: 1. Using a mouse with three or more buttons, assign one the "back" action to one of them using the default windows mouse control panel applet or the one that is installed with Intellipoint 3.2. 2. Open Mozilla and browse a few pages or so into any website 3. Click the mouse button that is assigned the "back" command to attempt to go back a page. Actual Results: Nothing happens. The same thing goes for the "forward" and "autoscroll" commands. The mouse wheel does work. Expected Results: These commands should be interpreted by Mozilla just as they are with Netscape and IE. Back button should go back one page, forward should go forward and autoscroll should bring up the autoscroll icon and scroll the page in all directions by moving the mouse. I have tested this with and without Intellipoint 3.2 installed and with two different mice (an older intellimouse 1.1A PS/2 and a new Intellimouse Explorer USB). Mozilla does not respond to the internet shortcut buttons when assigned to any of the mouse buttons. The mouse shortcut actions do work under Windows 2000. I have not had the opportunity to check Windows 98 or 95.
dup of bug 30431?
Marking as dupe of bug 30431. *** This bug has been marked as a duplicate of 30431 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Component: User Interface Design → Browser-General
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.