While many people might have another keyboard hooked up to their computer, that wasn't the case for me. You can be sure by disabling bluetooth (if your main keyboard is wired).

Other problems I've researched include: specific websites mess with CMD+Click via javascript either intentionally or accidentally. To debug, try a few different websites. If it's just one website that you really want CMD+Click to work on, there are some chrome extensions you can try, I haven't used any of them.

Make sure your CMD key works correctly. The OP in this thread did this via using CMD+0 or CMD+1 to navigate to different tabs.

Not sure what my issue was, but restarting the OS fixed it. Give that a try. Good luck.

Speculating here, but will confirm later from a Mac. This has been confirmed to be working on a Mac.

Win ctrl+click or a Mac command+click gets picked up by a "normal" click listener, just like a click with any other modifier key (alt+click, shift+click etc).

This is particularly confusing since a ctrl+click on a Mac gets interpreted as a right-click on OS level. Command-click, on the other hand, is not interpreted as a middle-click but rather is a browser preference.

Assuming that you do not have in-site functionality that specifically relies on modified clicks, it would be appropriate to exclude such events from click listeners, and instead allow for them to bubble up to be natively handled by the browser. Given the experience of someone in the similar situation, you should be able to add the following to click handlers (likely a delegate on library level as pointed out by Brilliand):

if (e.metaKey || e.ctrlKey) return;

When added at the beginning of the handler with e referring to a current click event, this should circumvent any following e.preventDefault();

Update:

It actually works! In this rather minimalistic fiddle, I am able to recognize when command-clicked or control-clicked, so as to avoid executing the rest of the click handler which includes ajax-fetching the content and e.preventDefault();. This allows for a command-click to be handled "as intended" on a Mac, i.e. opening the link in a new tab.

With this finding in mind, these lines should now read

if (e.isDefaultPrevented() || e.metaKey || e.ctrlKey) {
    return;
}

This is a puzzler and at first I was thinking, "wonky keyboard or keyboard controller."

But before I go blaming hardware it would be best to see if the issue is related to software.

Most, if not all, keyboard customizations are done on a user by user basis and if they are not set in System Preferences they would be set by something that ran at login or startup.

1. Restart your Mac while holding the ⇧ Shift key. When you see the Apple logo you can release the key. Startup may take a lot longer. If that fixes the issue there is something installed that is causing the issue. If nothing changes...
2. Create another user. Log in as that user. Still have the problem? Hopefully not. If not then there is something in your user profile messing with your keyboard. You can start deleting/moving/etc. preference files and the like, but I would be inclined to just migrate your files to the new profile and delete the old one.

Neither one of these worked? Add your results to your original question and we will take another stab at it.

Make sure when you press CMD+C your Edit menu in the top flashes, this indicates it works as expected.

If it doesn't, go to Keyboard settings in System Preferences and:

• Restore defaults Modifier Keys...,
• Restore defaults in Shortcuts tab,
• In App Shortcuts click the + button and test if Keyboard Shortcut input box will react on your combination.

If Edit menu flashes and it still doesn't work, then the first thing to do is to restart pasteboard service by the following commands:

launchctl stop com.apple.pboard
launchctl start com.apple.pboard

If still doesn't work, here are some other suggestions to troubleshoot the problem:

• Re-test in different applications just in case.
• Re-test if works when using contextual menu (without using the shortcut).
• Re-test alternative combination such as CMD+X for Cut instead.
• Run Console to see your System log queries if something obvious is happening.

• Test if the Clipboard works from the terminal via:

  $ echo test | pbcopy
  $ pbpaste
  

  If Paste menu item is no more greyed out, then maybe it's a problem with Paste command.

  If you're advanced user, use dtruss or fs_usage to debug it, for instance:

  $ sudo fs_usage | grep -C4 MyAppWhereCopyDoesntWork
  

  and then notice other apps which appearing exactly when you press the shortcut which potentially you could consider quitting for testing purposes.

• Disable any recent programs that you run or restart your computer.

• Disable VoiceOver as suggested here.
• Force quit the Finder (e.g.: killall -HUP Finder).
• If still doesn't work, consider rebooting the system, especially in Recovery or Safe mode to re-test.

As for a workaround, you can install Karabiner app and remap your shortcuts by configuring private.xml file (see Misc tab). For more suggestion, please check the following posts:

• Remap Ctrl+C, Ctrl+V, and Ctrl-X only
• How can I reassign the copy/paste keyboard shortcuts?

First and foremost, please note that in VS Code for macOS, the familiar Ctrl + click from Windows / Linux operating systems has been replaced with ⌘ + click (i.e.: "command + click"). Try that first before proceeding any further as that shortcut should work out of the box without any special modifications.

However, if the above still doesn't work for you then try fixing the problem by editing your settings.json file. To do that, press F1, type settings json, then click Open Settings (JSON), and then do one of the following:

To use ⌘ + click as your "Go to definition" shortcut, ensure the following line exists in your JSON settings:

"editor.multiCursorModifier": "alt",

What this does is it explicitly sets VS Code's "add another cursor" shortcut to option + click (try it out for yourself!), thus freeing up ⌘ + click to be used for the "Go to definition" operation.

Conversely, to use option + click as your "Go to definition" shortcut instead, add:

"editor.multiCursorModifier": "ctrlCmd",

Note: the above line will actually set the "add another cursor" shortcut to ⌘ + click (not Ctrl + ⌘ + click, as implied by the JSON value).