277312 - back "button" on touchpad does not work

Status: RESOLVED DUPLICATE of bug 56892

(Core :: Widget: Win32, defect)

Description

[Lisa]

Have a Dell laptop with Windows XP.  Can assign to an area of the touchpad the
"back" and "forward" buttons.  When in Firefox these do not work from the touchpad.

Comment 1

[timeless]

what mouse/keyboard driver is this? does it have a way to configure how those
behave per application?

Comment 2

[Gervase Markham [:gerv]]

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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[CMGaret_Jax]

I can confirm that thsi is still a problem.  I have a dell inspiron 600m with a
synaptics touchpad and apoint software.  Back and forward mouse gestures do not
work, and when I make the gestures in the browswer, the mouse does not move at
all.  This is most likely still an issue for everyone, we just sort of gave up
on it ever being fixed....

Comment 4

[Jo Hermans]

most likely a driver problem - see the comments in bug 56892

*** This bug has been marked as a duplicate of 56892 ***