Closed Bug 303480 Opened 19 years ago Closed 19 years ago

Change of behavior of middle mouse from 1.7.8 to 1.7.11

Categories

(SeaMonkey :: General, defect)

1.7 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: marciales, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 MultiZilla/1.7.0.1j
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 MultiZilla/1.7.0.1j

When I use the middle mouse, I always expected to open a new tab, and this
feature worked until 1.7.8 .I switch to 1.7.11 , and you have to right clik, and
from the menu select "open in a new tab" option to open the tab. Middle click
does nothing.

Reproducible: Always

Steps to Reproduce:
1.Open a page
2.middle click the mouse in a link
3.No tab is open

Actual Results:  
Nothing

Expected Results:  
Open the link in a new tab

Mozilla is behaving like Firefox. I like the old mozilla...
Do you see any error under Tools->Web Development->JavaScript Console when
clicking a link with middle mouse? Also i see you have MultiZilla installed, do
you see still this problem when using a second, new profile without MultiZilla
installed (start mozilla with mozilla.exe -profileManager and create a second
profile there; you can delete that test profile again after testing)?
This is very likely to be caused by MultiZilla. See:

http://bugzilla.mozdev.org/show_bug.cgi?id=10967

It's fixed in MultiZilla v1.7.9.0a (for Mozilla 1.7.x) and the latest MultiZilla
nightly (for the trunk/SeaMonkey 1.0a).

If the reporter of this bug does not check back, I think it is safe to mark this
one WORKSFORME.
I installed multizilla 1.7.9.0a in 1.7.8
Uninstalled 1.7.8
Reinstaled 1.7.11
The problem was gone. It was as pointed by Jens Hatlak , comment # 2, due to a
fixed bug in multizilla.
No Mozilla bug.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Version: unspecified → 1.7 Branch
You need to log in before you can comment on or make changes to this bug.