# Issues with Blockly 2.4.0

**URL:** <https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982>\
**Category:** General\
**Created:** [28 January 2024 08:15 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982 "2024-01-28T08:15:00Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![magicman](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@magicman](https://discourse.nodered.org/u/magicman)\
**Post date:** [28 January 2024 08:15 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/1 "2024-01-28T08:15:00Z")

</div>

Hi ,  
I have just installed Blockly 2.4.0 into my Node red and are have mouse issues with the node.  
If i click on any blockly item it moves into the workspace but then the block moves everywhere the mouse moves to , I cannot drop the block whatever button I click or key I press the block still moves.  
I cannot see what I am doing wrong ?

I have tried it on a Linux system and a windows system same problem  
i have also tried using Edge and Firefox browsers still the same problem

any help would be appreciated.

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [28 January 2024 10:02 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/2 "2024-01-28T10:02:33Z")

</div>

Are you using NR within Docker because there is an unresolved issue with it

> <https://github.com/bartbutenaers/node-red-contrib-blockly/issues/126>
>
> Hi, I just tried out the Blockly node and I like the concept. But I have the iss…ue 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. 
> 
> !\[Node\_Red\_Blockly\_Text\_Box\_Click\](https://github.com/bartbutenaers/node-red-contrib-blockly/assets/2019114/47b4a73b-b0b3-4367-887f-2311acc6a238)
> 
> 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?

Otherwise, I'm stumped as its all working fine of my Windows/Pi machines

But if not on Docker - what version of NR are you using - what version of node.js?

---

<div class="post-metadata">

**Author:** ![magicman](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@magicman](https://discourse.nodered.org/u/magicman)\
**Post date:** [28 January 2024 10:36 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/3 "2024-01-28T10:36:15Z")

</div>

hi thanks for replying,  
No not in docker

I am using NR V3.1.3  
Node.js V18.19.0

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [28 January 2024 10:39 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/4 "2024-01-28T10:39:47Z")

</div>

Is it the same effect as the Docker issue or can you not drop any block no matter where you grab it?

FYI I'm either on 18 or 20 on my machines - running node 19 is probably not the issue but maybe worth updating to v20 just to make sure

---

<div class="post-metadata">

**Author:** ![magicman](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@magicman](https://discourse.nodered.org/u/magicman)\
**Post date:** [28 January 2024 10:40 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/5 "2024-01-28T10:40:24Z")

</div>

yes it is the same effect just viewed that now

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [28 January 2024 10:41 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/6 "2024-01-28T10:41:23Z")

</div>

Lets see if moving to node v20 makes any diff then

---

<div class="post-metadata">

**Author:** ![magicman](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@magicman](https://discourse.nodered.org/u/magicman)\
**Post date:** [28 January 2024 10:41 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/7 "2024-01-28T10:41:57Z")

</div>

sorry i am on node 18 shall i still try 20?

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [28 January 2024 10:45 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/8 "2024-01-28T10:45:02Z")

</div>

Yep  
I just checked my Pi and it was on 20 and well as my windows machine

I don't think it'll be the cure but always nice to be on the same page 🙂

---

<div class="post-metadata">

**Author:** ![magicman](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@magicman](https://discourse.nodered.org/u/magicman)\
**Post date:** [28 January 2024 10:45 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/9 "2024-01-28T10:45:33Z")

</div>

ok thanks not sure how to do that but will look it up ;~)

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [28 January 2024 10:47 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/10 "2024-01-28T10:47:16Z")

</div>

On a debian linux machine- just run the installer script again with ---node20 on the end of it

On windows - go to node.js website and run the node20 installer

---

<div class="post-metadata">

**Author:** ![magicman](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@magicman](https://discourse.nodered.org/u/magicman)\
**Post date:** [28 January 2024 10:47 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/11 "2024-01-28T10:47:57Z")

</div>

thanks again! i will do it now

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [28 January 2024 10:58 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/12 "2024-01-28T10:58:40Z")

</div>

Just to check, I ran my Docker instance and got a bash shell inside it and it is using node.js v18 so it could just be the reason

---

<div class="post-metadata">

**Author:** ![magicman](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@magicman](https://discourse.nodered.org/u/magicman)\
**Post date:** [28 January 2024 11:06 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/13 "2024-01-28T11:06:02Z")

</div>

Hi me again 😉  
My linux machine fails on an install to node.js 20 so had to revert back to 18  
Need to get some work done now so will look into it again later.

Thank you so much for your time today

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [28 January 2024 11:31 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/14 "2024-01-28T11:31:22Z")

</div>

Well - I tried downgrading a Pi5 running bookworm to v18 - and I then I got the issue

Unfortunately - upgrading it back to v20 did not get rid of it!

So I'm a bit stumped now ☹

---

<div class="post-metadata">

**Author:** ![magicman](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@magicman](https://discourse.nodered.org/u/magicman)\
**Post date:** [28 January 2024 11:43 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/15 "2024-01-28T11:43:27Z")

</div>

opppsss sorry me bad!  
hope you get it working

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [28 January 2024 12:37 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/16 "2024-01-28T12:37:18Z")

</div>

For @BartButenaers when he pops in here  
On the non-working Pi5 instance I'm seeing this in the console if I'm just dragging a block around

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/2/52c7b3af2e3e1bcb1dfe4501d5d250a228bab5c4.png)  
(I don't get this in a working instance)

And then I get his error when I click in the text box (and unable to drop the block as per the Docker issue vid)

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/d/2dd9dd1a898177017e933f21816283499162ad5c.png)

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [28 January 2024 14:20 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/17 "2024-01-28T14:20:58Z")

</div>

Well - I just installed NR in a brand new Linux Mint VM and I get the issue ☹

So, The question is how come it is working fine on both an existing Pi and Windows that are running NR3.1.0/3.1.3 node V20 and Blockly node 2.4.0

---

<div class="post-metadata">

**Author:** ![magicman](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@magicman](https://discourse.nodered.org/u/magicman)\
**Post date:** [28 January 2024 14:39 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/18 "2024-01-28T14:39:31Z")

</div>

yes strange ? sorry i put you to all this trouble. Just glad it was not something silly i was doing.

---

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [28 January 2024 14:40 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/19 "2024-01-28T14:40:28Z")

</div>

> [@cymplecy](#):
>
> upgrading it back to v20 did not get rid of it!

Could it be that - by installing our node - you got a more recent (minor) version from the blockly package, which contains a bug?

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [28 January 2024 14:50 UTC](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982/20 "2024-01-28T14:50:29Z")

</div>

I'll have check on my Blockly versions

[Next page](https://discourse.nodered.org/t/issues-with-blockly-2-4-0/84982.md?page=2)