431053 - Command-Click on back button does not open new tab

Status: VERIFIED DUPLICATE of bug 350733

(Camino Graveyard :: Tabbed Browsing, defect)

Description

[Walker]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en; rv:1.8.1.14) Gecko/20080409 Camino/1.6 (like Firefox/2.0.0.14)
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en; rv:1.8.1.14) Gecko/20080409 Camino/1.6 (like Firefox/2.0.0.14)

In Mac OS X 10.5.2 in Camino 1.6 if a user command-clicks the back or forward buttons, nothing happens.  The button appears to depress, but there is no action performed by the browser.  Command-clicking should open up a new tab; as it stands it does not do anything.

Reproducible: Always

Steps to Reproduce:
1.hold down 'command key'
2.left click on 'back' button
Actual Results:  
new tab with previously visited page loaded does not load.

Expected Results:  
new tab with previously visited page loads.

Comment 1

[Stuart Morgan]

Command-click+drag is an OS-wide shortcut for rearranging toolbar items without using the customization sheet, so it does do *something* right now.

I think this is a dup of at least one other closed bug, but if we can reasonably intercept command-click for toolbar buttons then I think we should for everything that does navigation (back, forward, home, bookmarks, history); I'd much rather have command-click do what we want it to do than support a behavior that is at best marginally useful and more often accidentally destructive.

Comment 2

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

I think we'll have more people complaining about us breaking a standard OS behavior than complaining that cmd-click for "open in new" doesn't work.

Note also that we don't get a page or anything from Gecko, just "Go Back", which is why back/forward don't respond to Cmd- elsewhere in the UI (or at least Ian couldn't find a good way of getting at the URL when he was working on all of this).

Comment 3

[Chris Lawson (gone)]

The bug in question is bug 350733, and the reason we WONTFIXed this once already was because of consistency.