# Moving nodes via keyboard stops working

**URL:** <https://discourse.nodered.org/t/moving-nodes-via-keyboard-stops-working/101415>\
**Category:** General\
**Created:** [7 July 2026 05:27 UTC](https://discourse.nodered.org/t/moving-nodes-via-keyboard-stops-working/101415 "2026-07-07T05:27:39Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [7 July 2026 05:27 UTC](https://discourse.nodered.org/t/moving-nodes-via-keyboard-stops-working/101415/1 "2026-07-07T05:27:39Z")

</div>

Folks, I'm stuck.

I use Firefox - latest version.  
NR 4.9  
Ubuntu 22.04 LTS

Usually I select nodes and use SHIFT and arrows to move the node.

Now and then this stops working and the whole screen shifts.

What's going on and how do I get it back to moving nodes rather than scrolling the screen?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [7 July 2026 05:45 UTC](https://discourse.nodered.org/t/moving-nodes-via-keyboard-stops-working/101415/2 "2026-07-07T05:45:33Z")

</div>

Obvious questions first:

Node RED version?

Have you seen this behaviour with other node-red versions and/or other browser's?

Does it happen while in the middle of moving a node? After a certain amount of key presses?

Does it only happen after (for example) opening a node edit panel?

Does it continue to happen for ever more until you refresh the page?

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [7 July 2026 05:47 UTC](https://discourse.nodered.org/t/moving-nodes-via-keyboard-stops-working/101415/3 "2026-07-07T05:47:31Z")

</div>

NR 4.0.9

Sorry, missed the middle `0` in the first post.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [7 July 2026 05:49 UTC](https://discourse.nodered.org/t/moving-nodes-via-keyboard-stops-working/101415/4 "2026-07-07T05:49:32Z")

</div>

Yes, this happens from time to time with a lot of NR versions.

But I don't know what _triggers_ it.

It is _localised_ to THAT tab.

If I go to another TAB, the nodes move as expected.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [7 July 2026 05:52 UTC](https://discourse.nodered.org/t/moving-nodes-via-keyboard-stops-working/101415/5 "2026-07-07T05:52:50Z")

</div>

> [@Trying\_to\_learn](#):
>
> But I don't know what _triggers_ it.

By the sounds of that, it doesn't just happen in the middle of a move operation. I.e you're not in the middle of shifting a node pressing the keys and suddenly it stops working, right? It's more that you decide to move a node after some time of doing various tasks and it just doesn't work. Does that sound about right?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [7 July 2026 05:53 UTC](https://discourse.nodered.org/t/moving-nodes-via-keyboard-stops-working/101415/6 "2026-07-07T05:53:58Z")

</div>

> [@Trying\_to\_learn](#):
>
> this happens from time to time with a lot of NR versions

> [@Trying\_to\_learn](#):
>
> NR 4.0.9

A lot changed in node red 5. Do you have a version of node red 5 and have you seen it on that?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [7 July 2026 05:56 UTC](https://discourse.nodered.org/t/moving-nodes-via-keyboard-stops-working/101415/7 "2026-07-07T05:56:15Z")

</div>

> [@Steve-Mcl](#):
>
> Does it continue to happen for ever more until you refresh the page?

An answer here would be a good clue for us Andrew.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [7 July 2026 06:04 UTC](https://discourse.nodered.org/t/moving-nodes-via-keyboard-stops-working/101415/8 "2026-07-07T06:04:31Z")

</div>

Thanks,

I stupidly didn't think to try that.

Seems to have fixed it.

Sorry dude.

I'm getting a lot of brain farts these days.

Oh, it was a SHIFT RELOAD I did.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [21 July 2026 06:05 UTC](https://discourse.nodered.org/t/moving-nodes-via-keyboard-stops-working/101415/9 "2026-07-21T06:05:14Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.