322310 - Command-clicking on a bookmark in the bookmark bar (in a folder) doesn't open in new tab

Status: VERIFIED DUPLICATE of bug 317214

(Camino Graveyard :: Toolbars & Menus, defect)

Description

[Nick Forge]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051229 Camino/1.0b2
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051229 Camino/1.0b2

If you have a folder in the bookmark bar, (I have a folder called 'Forums') and Command-Click on a bookmark in the folder, it doesn't open in a new tab.

Reproducible: Always

Steps to Reproduce:
1. Make a folder in your bookmark toolbar
2. Put a bookmark in there
3. Command click on the bookmark from the bookmark bar

Actual Results:  
The bookmark opens, but in the current tab

Expected Results:  
It should open in a new tab

Comment 1

[Chris Lawson (gone)]

WFM whether I hold cmd from the beginning or press it after clicking the folder.

cl

Comment 2

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

WFM, too, 2006010304 (v1.0b2+), 10.3.9.

Comment 3

[Nick Forge]

By saying WFM, do you mean that the bug happens for you, or that the intended funcitonality works for you? It has stopped happening on my Camino now, and is consistently working as it should. Command clicking in a folder bookmark used to consistently NOT work as expected. Hmmm......

I don't think I ever tried pressing Command BEFORE clicking on the folder, so I'm not sure if that made any difference either.

Comment 4

[Nick Forge]

I noticed this bug while using my mouse which has it's middle-button assigned to Command-Click.

It appears that this is the same as Bug 317214, since my mouse would be replicating the behaviour described by this bug.

Sorry about the bug replication, I'm new to this.

*** This bug has been marked as a duplicate of 317214 ***

Comment 5

[Chris Lawson (gone)]

Just out of curiosity, what brand of mouse do you have? I wonder if this is specific to certain brands of mouse.

cl

Comment 6

[Nick Forge]

It's a Logitech MX-1000. This behaviour would happen with any form of macro that's doing a command-click though, mouse, keyboard or otherwise, since if you look at bug 317214 the problem is caused by Camino checking for the Command key status AFTER the mouse button is pressed. A macro will do a command-click instantaneously, so when Camino checks the command key 100-200ms after the button has been pressed, the command key has been released.