# 🎉 Node-RED 5 Beta 3 now available

**URL:** <https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505>\
**Category:** News\
**Tags:** docker\
**Created:** [5 March 2026 13:04 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505 "2026-03-05T13:04:20Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [9 March 2026 18:00 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/42 "2026-03-09T18:00:30Z")

</div>

> [@knolleary](#):
>
> The search highlighting is in need of suggestions as to what would be better.

Can you position the mouse pointer on the highlighted node?  
There is an option in Windows and Linux to highlight the cursor position when Ctrl key is pressed. I suspect this is turned on already for most people with eyesight problems, which currently does include me.

Can the highlighted node be placed at the centre of the editor screen?

---

<div class="post-metadata">

**Author:** ![mbonani](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mbonani/32/10631_2.png) [@mbonani](https://discourse.nodered.org/u/mbonani)\
**Post date:** [10 March 2026 11:07 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/43 "2026-03-10T11:07:43Z")

</div>

I just searched the code and found it was disabled.

> <https://github.com/node-red/node-red/pull/5510>
>
> \- \[\] Bugfix (non-breaking change which fixes an issue)
> \- \[x\] New feature (non-…breaking change which adds functionality)
> 
> \## Proposed changes
> 
> Resolves https://github.com/FlowFuse/node-red/issues/136
> 
> Full change set & manual testing plan \[here\](https://github.com/FlowFuse/node-red/issues/136#issuecomment-3991464121).
> 
> \## Checklist
> 
> \- \[x\] I have read the \[contribution guidelines\](https://github.com/node-red/node-red/blob/master/CONTRIBUTING.md)
> \- \[x\] For non-bugfix PRs, I have discussed this change on the forum/slack team.
> \- \[x\] I have run \`npm run test\` to verify the unit tests pass
> 
> We have an early return in \`sidebar.js\` but not introduced by my changes, appears intentional. Just noting it here. 
> 
> \`\`\`
> packages/node\_modules/@node-red/editor-client/src/js/ui/sidebar.js
> 408 | let tabBarButtonsBottom = tabBarButtonsContainer.position().top + tabBarButtonsContainer.outerHeight();
> ^ Unreachable 'let' after 'return'.
> 
> \>\> 1 error in 92 files
> \`\`\`
> 
> \- \[\] I have added suitable unit tests to cover the new/changed functionality

> <https://github.com/node-red/node-red/blob/dev/packages/node_modules/%40node-red/editor-client/src/sass/tabs.scss#L517-L519>

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [10 March 2026 11:14 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/44 "2026-03-10T11:14:16Z")

</div>

> [@mbonani](#):
>
> I just searched the code and found it was disabled.

Quite possibly an oversight when I reviewed the changes. Will revisit to see how it looks with the new tab style.

---

<div class="post-metadata">

**Author:** ![mbonani](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mbonani/32/10631_2.png) [@mbonani](https://discourse.nodered.org/u/mbonani)\
**Post date:** [10 March 2026 11:26 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/45 "2026-03-10T11:26:14Z")

</div>

I'm working on it now and can open a PR soon.

---

<div class="post-metadata">

**Author:** ![mbonani](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mbonani/32/10631_2.png) [@mbonani](https://discourse.nodered.org/u/mbonani)\
**Post date:** [10 March 2026 12:46 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/46 "2026-03-10T12:46:19Z")

</div>

Done.

> <https://github.com/node-red/node-red/pull/5552>
>
> \- \[x\] Bugfix (non-breaking change which fixes an issue)
> \- \[\] New feature (non-…breaking change which adds functionality)
> 
> 
> 
> \## Proposed changes
> 
> 
> 
> As discussed in the \[forums\](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/41), the fade effect for tab labels that overflow was mistakenly removed in #5510. This PR fixes that.
> 
> Additionally, the ugly SCSS variables I added in #3692 were removed, and the changes made to the linear gradients in 'tabs.scss' in 233a1995b3e29c59513792a37e4cbabf0007d4a4 were reverted. They were introduced as a workaround for a Safari issue that has already been resolved.
> 
> From \[Safari 15.4 Release Notes\](https://developer.apple.com/documentation/safari-release-notes/safari-15\_4-release-notes#:~:text=Fixed%20gradient%20color%20interpolation%20for%20colors%20with%20alpha%20transparency.) - March 14, 2022
> 
> \> Fixed gradient color interpolation for colors with alpha transparency.
> 
> Editor screenshots with the fix:
> 
> \<table\>
> \<tr\>
> \<td\>
> \<td\>Vanilla
> \<td\>Dark (Midnight)
> \<tr\>
> \<td\>Chrome
> \<td\>\<img width="961" height="541" alt="image" src="https://github.com/user-attachments/assets/74f72fe1-b345-4669-bdc1-59ec8e2b890a" /\>
> \<td\>\<img width="961" height="541" alt="SCR-20260310-hlyd" src="https://github.com/user-attachments/assets/c02d1dcb-1370-4d24-b461-e0d4221c4374" /\>
> \<tr\>
> \<td\>Firefox
> \<td\>\<img width="961" height="541" alt="SCR-20260310-hmnp" src="https://github.com/user-attachments/assets/ba47ae22-50a4-4cd8-a3a9-ff5c9cbeb3ad" /\>
> \<td\>\<img width="961" height="541" alt="SCR-20260310-hlzn" src="https://github.com/user-attachments/assets/c0acfbec-84a3-416d-910e-db80b5d24fad" /\>
> \<tr\>
> \<td\>Safari
> \<td\>\<img width="961" height="541" alt="image" src="https://github.com/user-attachments/assets/a2be6e5c-bc62-4c2f-bfc5-e33eee71f9ce" /\>
> \<td\>\<img width="961" height="541" alt="SCR-20260310-hmag" src="https://github.com/user-attachments/assets/d44c9426-419a-48f1-a054-090589dc51d7" /\>
> \</table\>
> 
> \## Checklist
> 
> 
> \- \[x\] I have read the \[contribution guidelines\](https://github.com/node-red/node-red/blob/master/CONTRIBUTING.md)
> \- \[\] For non-bugfix PRs, I have discussed this change on the forum/slack team.
> \- \[\] I have run \`npm run test\` to verify the unit tests pass
> \- \[\] I have added suitable unit tests to cover the new/changed functionality

---

<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:** [10 March 2026 15:23 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/47 "2026-03-10T15:23:53Z")

</div>

Hi Nick.

I dont want to be "that guy" (again) but NR5 beta still does not scroll the workspace horizontally with modifier + mouse wheel.

I know it was mentioned (and acknowledged) on a prev beta but cannot see an issue in the NR tracker (happy to admit my search foo may be off its game but I did search a few terms)

For reference: In NR4 and below, `SHIFT` + mouse scroll scrolls the workspace horizontally. In NR5 betas, the `SHIFT` modifier does not seem to work (workspace continues to scroll vertically)

* * *

Chrome latest on Windows 11.

* * *

Happy to raise an issue too if required.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [10 March 2026 15:58 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/48 "2026-03-10T15:58:25Z")

</div>

> [@Steve-Mcl](#):
>
> For reference: In NR4 and below, `SHIFT` + mouse scroll scrolls the workspace horizontally. In NR5 betas, the `SHIFT` modifier does not seem to work (workspace continues to scroll vertically)

Shift-scroll is scrolling horizontally for me with the beta on Chrome and Firefox on Mac.

Maybe a windows specific thing...?

---

<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:** [10 March 2026 16:16 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/49 "2026-03-10T16:16:09Z")

</div>

> [@knolleary](#):
>
> Maybe a windows specific thing

I dont think so Nick:

- firefox same: [🎉 Node-RED 5 beta.0 released - #42 by JoW](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/42)
- Ubuntu same: [🎉 Node-RED 5 beta.0 released - #45 by Colin](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/45)

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [10 March 2026 16:19 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/50 "2026-03-10T16:19:18Z")

</div>

I see the problem too, with Brave and Edge on Ubuntu with Gnome. The shift key appears to have no effect with the scroll wheel.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [10 March 2026 16:34 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/51 "2026-03-10T16:34:54Z")

</div>

So basically, every OS/browser other than the combination I tested with....

Issue raised: [UX: Shift-scroll not scrolling horizontally for some OS/browsers · Issue #5557 · node-red/node-red · GitHub](https://github.com/node-red/node-red/issues/5557)

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [10 March 2026 17:41 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/52 "2026-03-10T17:41:22Z")

</div>

> [@knolleary](#):
>
> So basically, every OS/browser other than the combination I tested with....

So its a Mac thing then. 😉 🤣

Safari, the new IE. ☹

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [10 March 2026 17:43 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/53 "2026-03-10T17:43:26Z")

</div>

Curiously, this was Chrome on Mac. Either way, the fix is in (and confirmed by Steve) - [Handle shift-scroll more robustly by knolleary · Pull Request #5559 · node-red/node-red · GitHub](https://github.com/node-red/node-red/pull/5559)

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [10 March 2026 17:59 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/54 "2026-03-10T17:59:26Z")

</div>

Experimenting with a better node highlight appearance:

1. Use a halo around the node, rather than just its existing border - a better visual target to spot.
2. Doesn't flash - could be contentious...
3. Says in place for ~5s and then fades out.

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

Thoughts?

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [10 March 2026 18:02 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/55 "2026-03-10T18:02:30Z")

</div>

> [@knolleary](#):
>
> Thoughts?

Certainly an improvement in my view. 👍

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [10 March 2026 18:14 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/56 "2026-03-10T18:14:36Z")

</div>

Maybe 10 seconds?

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [10 March 2026 18:24 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/57 "2026-03-10T18:24:45Z")

</div>

If the mechanism is that the target node temporarily acquires a class "targetted" then we could highlight it as we wish via CSS, right up to throbbing and spinning if that meets our accessibility criteria.

---

<div class="post-metadata">

**Author:** ![duaw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/duaw/32/20970_2.png) [@duaw](https://discourse.nodered.org/u/duaw)\
**Post date:** [10 March 2026 18:38 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/58 "2026-03-10T18:38:13Z")

</div>

> [@knolleary](#):
>
> Thoughts?

Honestly, I sometimes find the node only and/or only fast BECAUSE it "flashes".

I call the current "flashing" subtle, not flashy. Perhaps an animation in a non obtrusive moving ants style?

I don't want to be offered more time findig the node. I want to find it fast.

BTW: A halo must not collide w/ node status etc.

A single "highlighted" (is this proper English?) node could be centered on the workspace w/o need of any further scrolling. Right now its location on the screen seems … random..

Cheers, Uwe

---

<div class="post-metadata">

**Author:** ![LosinIt](https://avatars.discourse-cdn.com/v4/letter/l/439d5e/32.png) [@LosinIt](https://discourse.nodered.org/u/LosinIt)\
**Post date:** [10 March 2026 20:53 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/59 "2026-03-10T20:53:24Z")

</div>

How about making it configurable?

---

<div class="post-metadata">

**Author:** ![jf64](https://avatars.discourse-cdn.com/v4/letter/j/b19c9b/32.png) [@jf64](https://discourse.nodered.org/u/jf64)\
**Post date:** [11 March 2026 13:26 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/60 "2026-03-11T13:26:28Z")

</div>

1. The color shall be one which is not common in the editor or e.g. an "inverter" color.
2. Test it please also in zoomed out editor. Even there it shall be good recognizable.
3. Better to use a thick line than a thin one.
4. Since you cannot do it that way that everyone will like it, try to make it as configurable as possible (and then you will see, people won't use the configuration).
5. I could image it also that way, that the cursor will be moved (additionally to those visual effects) to the node (but this feature must be configurable or a checkbox in the search form!), thus, a double click with the mouse would always open the found node.
6. At the very end every improvement to the current situation would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![Marooned](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marooned/32/2858_2.png) [@Marooned](https://discourse.nodered.org/u/Marooned)\
**Post date:** [12 March 2026 12:15 UTC](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505/61 "2026-03-12T12:15:53Z")

</div>

I know a random opinion from the internet won't change anything, but the previous UI and UX had much more sense to me.

Tabs in the browser and tabs in the Node-RED were working like briefcase tabs, connected visually with the content.  
I click on the tab to see the page [in the browser].  
I click on the tab to see nodes [in NR].  
From top to bottom, like a proper hierarchy,

The new buttons are visually disconnected from the content, does not resemble mentioned logical briefcase tabs. Also, part UI for selecting content is on top [tabs, sorry - buttons for the editor], some on the bottom [tabs for the side panel] - striking lack of consistency.

My vote won't change the roadmap but still decided to write about it.

 ![tabs](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/7/f7e04d312b7712400a058c0e401df189b13d71af.png)

[Previous page](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505.md?page=2)

[Next page](https://discourse.nodered.org/t/node-red-5-beta-3-now-available/100505.md?page=4)