637068 - Bad excecution of Exit/Close function signaled by custom button on the Microsoft Wireless Laser Mouse 7000

Status: UNCONFIRMED

(Core :: Widget: Win32, defect)

Description

[Laurens]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
Build Identifier: Minefield 4.0b13pre

The browser exits (when multiple tabs are open) when the "Close" function of the Microsoft Wireless Laser Mouse get's excecuted. The execution happens when one of the custom buttons is pressed. This should only happen when the button is set to the "Exit Program" function.

The latest stable release (in the 3.6 branch) still closes a single tab.

Reproducible: Always

Steps to Reproduce:
1. Have multiple tabs open.
2. Press custom button -> driver sends "Close" signal.
3. Browser exits.
Actual Results:  
The browser closes in it's entirety.

Expected Results:  
The current tab should close.

The actual driver is updated and the configuration has been reviewed.

No extensions, except "User Studies". Default theme. "Standard" plugins, nothing special.

Comment 1

[Matthias Versen [:Matti]]

and which message does this mouse driver send to Firefox ?
This is most likely a mouse driver bug caused by the updated UI or window structure

Comment 2

[Laurens]

(In reply to comment #1)
> and which message does this mouse driver send to Firefox ?
> This is most likely a mouse driver bug caused by the updated UI or window
> structure

It has nothing to do with the Window appearance of a particular program.

It is a message similar to *nix's "kill"; ie. a message send directly to the process (in this case Firefox). It was always interprented by Firefox as "Close current tab". Now, the whole process just get's cancelled.

It is a misbehaviour in the way Firefox executes an assignment, ie. a bug with the browser, not with the mouse driver.

Comment 3

[Matthias Versen [:Matti]]

>It is a message similar to *nix's "kill"; ie. a message send directly to the
>process (in this case Firefox). It was always interprented by Firefox as "Close
>current tab". Now, the whole process just get's cancelled.

How do you know that ?

>It is a misbehaviour in the way Firefox executes an assignment, ie. a bug with
>the browser, not with the mouse driver
Again, how do you know that if you don't know which events are send to Firefox ?

How about this: The driver doesn't detect Firefox anymore as application with tabs and sends now a window close command instead of a tab close command 

There is no API in windows for this additional mouse features (and that includes mouse srolling!) and there is nothing that you can do wrong in Firefox to break such a feature.