ID 308316 - Using a 'CTRL/CMD' create node command on a selected node replaces it - (Nuke11 Mac)

Problem summary
When a user assigns a hotkey to a CTRL/CMD  function, they may have a chance of replacing any selected node.

This appears to be a new issue with Nuke 11 for Mac systems.

As an example: If a hotkey to create a 'Text' node with 'CTRL+T' is initiated,  If the user selects another node (Expecting the text node to be linked underneath), it will replace the selected node.

Customer reported version
nuke.11.0v2

Customer reported platform
10.11

Steps to reproduce

1) Open Nuke and navigate to a 'Script Editor' window

2) Place and execute the following code:

menubar=nuke.menu("Nuke")
m=menubar.addMenu("Custom")

m.addCommand('Old Text', "nuke.createNode('Text','font %s box {50 147 2098 1005}' % 'Regular.ttf')", 'ctrl+t')

3) Create a 'Grade' node

4) Select the 'Grade' node and initiate the shortcut (CTRL+t)

Result: The 'Grade' node will be replaced with the new 'Text' node.

Workaround

Option 1: Use 'Shift' OR 'Alt' instead.
Option 2: Click where you would like the node to be placed and manually link the nodes.

Reproduced by support
Nuke11.0v2 - Mac10.12
Nuke11.0v1 - Mac10.12

Could not reproduce:
Nuke11.0v2 - Windows 7 - CentOS6.9
Nuke11.0v1 - Windows 7 - CentOS6.9
Nuke10.5v5 - Windows 7 - CentOS6.9
Nuke10.0v6 - Windows 7 - CentOS6.9

Earliest version tested
Nuke10.0v6 - Could not reproduce the issue, didn't expect issues in earlier versions.

Expected behaviour
When using 'CTRL/CMD' in a hotkey assignment, the function shouldn't replace the selected node.

Actual behaviour
The hotkey replaces the selected node.