Open DirkScharff opened 8 months ago
I don't seem able to repeat the behaviour your seeing (Win11/Vivaldi)
I made the gif on Win10.
I just tried on my mac and it happens with chrome and safari there too. So i guess it must have to do something with my NodeRed instance or the Node. I am using NodeRed in docker.
computers!!!!! :(
I just tried with a completely fresh NodeRed Docker instance. => not working I downgraded the fresh instance to NodeRed 3.0.0 => not working I installed node-red-contrib-blockly@2.0.0 => working upgraded to 2.4.0 again and restarted nodeRed => not working uninstalled 2.4.0, installed 2.2.0 => not working installed 2.0.0 again => working installed 2.1.0 => not working installed 2.0.0 on NR3.1.3 (production setup) => working
So I guess I am stuck on 2.0.0 for now.
I'll see if I can install Docker on my Pi5 and see what happens
FYI The machine I tested out on is running 3.1.0/2.4.0
I guess its unrelated (at least I don't see a connection) but I am running NodeRed on an Unraid machine using the official NodeRed containers.
I get the same behaviour as you with the docker version (3.1.3/2.4.0) on my Pi5
Thanks for trying. At least it is reproducible then.
This is probably going to be a core Blockly issue as those block are standard Blockly - not special ones that Bart has added for NR
See this thread for info https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982?u=cymplecy
Hi, I just tried out the Blockly node and I like the concept. But I have the issue you can see in the gif. When I click on something where I would expect a div switching for an editable component the node instead starts dragging and I can not drop it anymore without closing the editor.
The Javascript console gives the following error:![image](https://github.com/bartbutenaers/node-red-contrib-blockly/assets/2019114/b646aa1e-70a4-4abd-a0f9-577b9d726e44)
NodeRed version is 3.1.3 and node-red-contrib-blockly at 2.4.0 Happens with Firefox and Chrome. Any Ideas?