Open Bug 164008 Opened 22 years ago Updated 12 years ago

Middle - click on the location bar history menu should open a new tab

Categories

(SeaMonkey :: Tabbed Browser, enhancement)

Product:
SeaMonkey
Component:
Tabbed Browser
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

People

(Reporter: serval, Unassigned)

References

(Blocks 1 open bug)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1b) Gecko/20020721
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1b) Gecko/20020721

When middle-clicking on the history menu that appears under the location bar,
nothing happens. It should be nice to see the middle-clicked website in a new tab.

Reproducible: Always

Steps to Reproduce:
1. Click on the arrow at the right of the location bar
2. Middle-click on a website in your history menu


Actual Results:  
Nothing happens

Expected Results:  
Mozilla should show up the middle-clicked website in a new tab.
So, what's wrong with the right click?  Would it be worth it to make it more 
mixed it with new features for middle click in addition to the right click?  
What about the 2 button mouse where newbie never heard of a middle click?  Just 
some thoughts here.  :-)  No hard feeling!
Thanks for the comments.

I think it is better to keep things consistent: 
 * Right click is for the context menu
 * Middle click and ctrl-click are there to open a new tab

Using the right mouse button to open a link in a new tab will confuse the
newbies more, IMHO.

Probably it is a good idea to add a context menu to the history menu of the
location bar. That context menu could have some nice features like 'open link in
new tab' or 'remove this link from history menu'
QA Contact: sairuh → pmac
*** Bug 190294 has been marked as a duplicate of this bug. ***
confirming as I have found no dupe, and adding dependency
Blocks: link-modifiers
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
*** Bug 257601 has been marked as a duplicate of this bug. ***
Requesting blocking-aviary1.0.
Flags: blocking-aviary1.0+
Please do not set the blocking-aviary1.0+ flag. the + flags are reserved for use
by drivers@mozilla.org or the Aviary team.
Flags: blocking-aviary1.0+
My apologies. I was unaware and assumed that I wouldn't be able to set a flag if
I wasn't intended to. I'm also assuming anyone can set a ? flag. Which is what
I'm doing. Apologies if I'm out of line again. And if I am, could someone please
direct me to a list of rules via email?
*** Bug 277700 has been marked as a duplicate of this bug. ***
Flags: blocking-aviary1.1?
Flags: blocking-aviary1.1? → blocking-aviary1.1-
Flags: blocking-aviary2.0?
not a blocker for Firefox 2, but it would be nice to have
Flags: blocking-aviary2? → blocking-aviary2-
Assignee: jag → nobody
Flags: blocking-firefox2-
Flags: blocking-aviary1.5-
QA Contact: pmac → tabbed-browser
Product: Core → SeaMonkey
Fixed in bug 529240
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
No it's not; while that bug did fix the go menu and the back, forward and reload buttons it did not cover the location bar history menu.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Status: REOPENED → NEW
You need to log in before you can comment on or make changes to this bug.