Users are unable to edit node configuration in windows chrome.
Cause of the issue: Chrome fires a mousemove event along with click event on each node click.
Effect: We use mousemove event to differentiate between click and drag event (when a node is dragged around and when a node is clicked). If a mousemove event is fired everytime a click happens we detect it as drag event and ignore opening node config modal. This is what is causing the issue that users see in windows chrome.
Reference to actual chrome bug: https://bugs.chromium.org/p/chromium/issues/detail?id=161464