199639 - Latest Logitech mouse drivers 9.76 breaks middle-click functionality

Status: RESOLVED INVALID

(Core :: Widget: Win32, defect)

Description

[john_pub_mail1]

User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.3) Gecko/20030312

Using the latest Logitech drivers 9.76 and a mouseman wheel, tab funtionality no
longer works correctly. When opening a tab using middlemouse button, a tab opens
correctly in the background, but if there is any history in the parent pane, the
page goes back one.

Tabs still work correctly when using CTL-leftclick rather than middle mouse.

Reproducible: Always

Steps to Reproduce:
1. Set Mozilla to open a tab in the background when using middlemouse button.
2. Go to any web page
3. click though a link or two to get some navigation history
4. start opening links into tabs in the background using middlemouse button
Actual Results:  
Tab opens successfully, but parent window flips back though the history as if
you have clicked the "back" navigation control.

Expected Results:  
Mozilla should have opened tab in background and parent pane should not have
changed.

Logitech driver is latest 9.76.
Mouse is Logitech optical mouseman wheel.
OS is WinME.

This worked previously with older drivers, so cold easily be a Logitech issues,
or it is possible that new mouse drivers are triggering a fault in the way
middlemouse tabs are handled. 
Logitech are one of the most popular mouse manufacturers, so it is worth a fix.

Comment 1

[john_pub_mail1]

Just noticed that clicking middlemouse button *anywhere* in a Mozilla window
causes a jump back one page in the history. Is this intended behaviour, or are
Logitech incorrectly sending a "back one page"?

Comment 2

[Jason Bassford]

Interesting.  I'd just installed those drivers prior to seeing this bug. 
However, I've always set my middle button to behave as a double-click, so this
bug doesn't really apply to me.  But, in the interest of investigating, I
changed it to "Middle Button".  After doing that, Mozilla does nothing at all
for me when I middle-click on a link.  (Yes, I've set that preference.)  So,
unless I'm configuring my mouse / Mozilla incorrectly, the functionality on my
computer is totally broken.

I'm using XP and the 3/27-04 build.

Comment 3

[john_pub_mail1]

After a bit more experimentation, it seems that any "middlemouse" message sent
from these new drivers trigger a "back button navigation" from Mozilla 1.3 (at
least on my WimME system).

It's *really* annoying, as it breaks the "middlemouse opens tabs" funtionality,
one of the best things about browsing with Mozilla.

Comment 4

[john_pub_mail1]

After a bit more playing around, I *suspect* this is caused by Logitech trying
to be clever. They decided that any middlemouse button should trigger a back
navigation in Netscape/Mozilla, not realising that this clashes greatly with the
"middlemouse opens tab". They do something similar with IE where middlemouse
triggers an autoscroll function. 

There is no way to disable these two features in the Logitech mouseware control
panel, so manages to continue with the general "fix a bug, make a bug" that
Logitech mouse drivers seem to follow.

Is there anyway for Mozilla to block this "feature" of Logitech's Mouseware? I
have already found and mailed them on a email address that does not involve
jumping through web-hoops ([e-mail]). 

I have also tried a workaround by placing Mozilla in the registry group for
"gaming compatability * ", which does work, but disables all other mouse
features such as accelleration. This feature does enable middlemouse to work
without a "back navigation", so strongly indicates the problem is one of the
"special features" which Mouseware implements. 

*[Gaming compatability was included by Logitech to automatically disable these
mouseware extras when they interefered with gaming IO. It seems that Mozilla now
has the same problem due to Logitech deciding unilaterally that all Mozilla
users doing a middlemouse click actually want to do a "back navigation".]

Comment 5

[Chris Casciano]

confirming based on multiple reports... this may morph into an evangelism bug if
its deemed theres no workaround to be done on mozilla's part

Comment 6

[Jason Bassford]

FWIW: I reverted back to 9.75 and was STILL unable to use the middle (scroll
wheel) button in Mozilla when I'd defined it as "Middle Button" rather than my
normal double-click.  So my report in comment 2 about that not working wasn't
pertinent to 9.76 at all, but simply something to do with my general setup.

However, having said that, I was having significant problems with 9.76 that had
nothing to do with Mozilla.  It would only "think" I had a middle button for an
hour or so, then that functionality would suddenly disappear and the UI in the
mouse control panel applet would no longer offer me the option of configuring my
middle button.  Rebooting did no good.  After a reinstall of 9.76, the middle
button "came back" but, again, only for an hour or so before it disappeared. 
(I've never seen anything like this before.)

So it seems that the Logitech software is simply buggy, whether or not Mozilla
is thrown into the equation.  Since it's having problems that have nothing to do
with Mozilla, I suspect that they're going to have to release a "fix" shortly. 
Also, I believe that this should really be marked INVALID, and not even
Evangelism.  But I suppose we could wait and see how it plays out.

Comment 7

[john_pub_mail1]

It does seem to be that Logitech is arbitrarily buggering about with the
behaviour of Mozilla. They probably thought it would be good to have the default
middlemouse  have a browser-back navigation function, but were too dumb to
research it properly, and thus neglected to take into account the "middlemouse
opens tab" functionality. This is par for the course for Logitech. I'm now more
inclined to belive it is a Logitech mis-design, rather than a direct Mozilla
problem. 

Comment 8

[Michel Poleur]

I received this message today, from Logitech support after I complained. In
short, it says it's normal the mouse is not functioning because Mouseware is
compatible with IE and Netscape Navigator only. No update will be released to
correct the problem.




   Cher Monsieur Poleur ,

   Nous vous remercions pour votre mail et de l'intérêt porté à l'égard des
produits Logitech.

Votre souris Logitech ne fonctionne pas correctement sous Mozilla 1.5 après
l'installation de MouseWare 9.76. Cela est tout à fait normal car ce
logiciel est compatible uniquement avec les navigateurs Internet Explorer
et NetScape Navigator. Aucune mise à jour du logiciel Mouseware n'est
malheureusement prévue pour fonctionner correctement avec le navigateur
Mozilla.



Pour toutes autres questions ou informations complémentaires, n'hésitez pas
à nous recontacter.

Afin d'assurer un meilleur suivi des communications, nous vous demandons de
conserver l'intégralité du message ci-dessous dans votre réponse et
d'ajouter votre nouveau message au-dessus.


Sincères salutations.
***name removed***
Logitech Customer Support

Comment 9

[john_pub_mail1]

I found that after upgrading to Windows XP, with no Logitech drivers (ie just
the default Microsoft drivers), the middlemouse buttons sends a "back one page"
broken behaviour as above.  After installing the Logitech drivers, the
middlemouse button assigned to "middlemouse" through the Logitech drivers gives
the correct results with the last few Mozilla releases (1.4 and higher).

Although I did send a bug report to Logitech and chased it up a few times, I've
never been able to get any kind of useful response.

Comment 10

[Tim Meader]

Confirmed fixed for me on Firefox 0.8 and Mozilla 1.7b if you set the
functionality of the middle mouse button to "Middle Mouse Button" in the
Logitech drivers instead of the default "Universal Scroll". This is with
Logitech Mouseware v. 9.79.1

Comment 11

[Michel Poleur]

It works for me too, with "Middle button" set and Mouseware 9.79.025.

Comment 12

[Nickolay_Ponomarev]

*** Bug 270067 has been marked as a duplicate of this bug. ***

Comment 13

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)(away until 10/14)]

This bug couldn't be our bug. And fixed by upgrading SetPoint to latest version in 2004. So, we should mark this bug as INVA.