Command + click to open link to new tab won't work (Sierra)

1. US keyboard that comes in MacBook Air 2014 and MacBook Pro 2012 (the CMD + Click on a link doesn't open a new tab in both machines)

2. Yes, in my case, bottom right. It will show as grey instead of white when CMD is pressed once, white when pressed twice. Pressing CMD 2x + Click on a link would open a new tab.

Nothing at all. Just the built-in keyboard. Sticky keys is that way. You press it once, it only "sticks" for one mouse click/keyboard press (grey). Press it twice, it becomes "sticky" (white) and stays for until you press it the third time.

favoriteno4 wrote:

Nothing at all. Just the built-in keyboard. Sticky keys is that way. You press it once, it only "sticks" for one mouse click/keyboard press (grey). Press it twice, it becomes "sticky" (white) and stays for until you press it the third time.

Just tried this on my mac (didn't know about pressing twice).

I find that with the double press (the command symbol becomes white), then the next click works.

Just a single press, and no matter how quickly or slowly I click, it does not command-click.

This is exactly my point. Previously, pressing CMD 1x (grey symbol) and left click (or single tap on trackpad) would open a new tab. It doesn't do that anymore in this new OS. This is what I'm trying to find the fix for.

favoriteno4 wrote:

When you say "work", do you mean you're able to open a new tab when you press the command button ONCE, release it, and click on a link?

FWIW, I assume everyone knows you can't click somewhere else first, i.e. click on a tab to get to a link. For that, you would have to press the command key twice.

Mine was also already checked at the first place. But by unchecking and then checking it worked for me.

And I use Safari and Firefox mostly on my side, after re-checking the option in Safari, it now works in both Browsers, while it wasn't working after upgrading to Sierra.

I just checked and confirmed that it now also works in Chrome.

Bluefurry wrote:

It's rather annoying, almost as though it was purposefully disabled to force me to move to an apple keyboard

Seriously? I imagine Apple has better things to do than test all third-party keyboards and re-write their OS to cripple them just so they can make a few dollars.

Does your keyboard use drivers?

I did say "almost like" I know they wouldn't do it on purpose...

If it were the keyboard drivers, then command-click wouldn't work within VMWare would it? The keyboard doesn't use any special drivers other than the USB Keyboard driver included in the underlying system.

Please disregard the snide comment I made and stick with the issue 🙂

Bluefurry wrote:

If it were the keyboard drivers, then command-click wouldn't work within VMWare would it? The keyboard doesn't use any special drivers other than the USB Keyboard driver included in the underlying system.

🙂

Another way to look at the issue is, if it's because of Sierra why would it work in VMWare?

All I know is as I mentioned a few times in this thread is, I have Sierra installed on three different Macs and command + click works for me. Two are laptops which I wouldn't normally use with an external keyboard. I do have Apple wireless keyboards which even if they do work (I haven't checked), really wouldn't answer your question.

You could try creating a new user and test. You could start in Safe mode and test. I assume you tried what has worked for others in this thread. Sometimes a problem occurs which makes no logical sense is is hard to track down.

The best work around yould have been sticky keys, unfortunately Sticky Keys doesn't seem to work with my keyboard, works on the laptop keyboard of course, but that's out of reach.

Where I really need the functionality is in my IDE, where I use command-click to navigate code, for browsing it was just a nice feature, but not really important. Guess I'm SoL until apple or ckb comes out with a fix.

Good news, I've finally got a solution. Sierra knows about the Corsair Strafe RGB now, however, if you've ever installed ckb to get the lights working, then ckb-daemon interferes with the modifier keys in some way.

Here's the check and fix:
1. Confirm this is the problem: check for the process "ps ax|grep ckb-daemon" (no quotes) if it's the issue, you'll see ckb-daemon running. If it's not, don't bother with the rest of these instructions, this isn't the solution you're looking for.

2. Delete ckb from Applications: open a Finder window, click on Applications, find ckb, and trash it

3. Kill ckb-daemon: either restart your mac or execute "sudo killall ckb-daemon" in a shell

4. Confirm it's no longer running by checking for the process again: "ps ax|grep ckb-daemon" you should only get one line back showing the command you ran

I hope this helps those frustrated by this. Unfortunately this fix loses any cool lighting features of the Corsair keyboards, leaving it only backlit by white.

For what it's worth, I had a similar problem: holding command + left click was not working to open links in new tabs

(I never used the "sticky key" variant). This was even though holding down the command key would show the prompt in the Safari status bar, that clicking the link would open in a new tab (it wouldn't). And the command key itself seemed to work in all other ways just fine.

In the end I believe it had something to do with a key-modifier App I had installed (Karabiner-Elements). I quit this, restarted the app, and let it update, and then my normal command-clicking to open link in new tab behaviour returned to normal.

So if you are having this problem, check if you have any apps running that do key-modification, because they could be interfering with the normal behaviour.

good idea…

It works quite well here running Sierra and Safari. Do you have your Tab bar enabled? Check under Safari's View menu.