n8n EXECUTIONS_PROCESS setting (default: own, main): main
Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
Operating system: Alpine docker/ RedHat host
Hello,
Since the update in v 1.27.1 it is not possible to select one node by clicking on it. When we click on a node, it is not surround (like it was in previous version) and all keyboard shortcut (shift right, ctrl click to select nodes) doesn’t work either.
Does anyone else have the same issue with the version 1.27.1 ?
I’m not able to reproduce this so far. Can you please share more information about what browser you are testing this on?
Also, have you tried reloading the UI to see if that fixes the issue?
I try with Firefox, Edge and chrome and I can’t select a specific node when I click on it since the update. One of my collegue try with another computer and he had the same problem. When we click the node is not selected but when we maintain the click we are able to move the node
I’m unfortunately still not able to reproduce this on Firefox or Chrome. Maybe this is specific to a node type.
Can you share a screen recording with us? if not, maybe a screenshot?
We can’t seen on video when I click but I click several times on the MySQL Node and then on the “Split Out” node. Event when I move the node you can see it’s not surround.
We have had a few issues with touch enabled screens in the past, I suspect this could be related to that. Do you have a machine without a touch screen you can test on?
Interesting, I have never seen this happen on a device without a touchscreen. What device are you using to access n8n and do you have the same issue in private browsing mode?
It would also be interesting to see the output of the browser dev console to see if anything odd is there.
When I click and hold, the <body class"katavorio-drag-noselect"> is added to the DOM, but when I release, the node remains unselected. When I click it comes and goes really fast.
There is nothing in the console when I click around, try to select, or try to multi-select. I just noticed the upgrade - completed the upgrade - problem persists.
There is a css class wrapping the node “is-touch-device” - once I removed that everything started working for all nodes.
I think I might be a one-off case as I checked https://www.deviceinfo.me/ and it does say my browser supports touchscreen for some reason. I appreciate your efforts - but I also respect your time too much. I will figure this out and come back with better information and a solution.
