Strange editor UI labellings

Dashboard
1

An interesting UI phenominon after updating to v4.0.9.

I have found no information via Googling, and am not even
certain exactly how I would research it properly-!

Happening on a Nanopi Fire 3, a raspberry pi 4 and a Windows 10 PC.
It is apparently not destabilizing, just visually peculiar
as I've never seen the phenomenon occur before,
and am wholly uncertain of how to correct it
before I pursue any further edge device updates.

Screenshot 2025-06-17 042905
Screenshot 2025-06-17 042905681×849 27.7 KB

Any ideas / recommendations / advice?

2

Did you have refreshed your browser?

3

Yes, caches cleared and visited from other physical Internet locations with Chrome, Chromium and Edge, all with the same result - it is text being served by various updated Node-RED installs.

4

Is this only happening on the Dashboard sidebar, or also elsewhere too?

5

Erm, not sure what I am supposed to be looking at here, my Dashboard 2 sidebar looks exactly the same?

6

I have seen that too in the dashboard sidebar, but do not have access to my PC at the moment to investigate.

7

DB 1.24.2
NR 4.0.9 & 4.1

Same issue. Only related to DB2 Sidebar.

@joepavitt, ui_template must be replaced by ui-base

8

All three affected edge devices apparently exhibit the phenomenon only in the sidebar.

9

I am facing the same - since last DB2 upgrade.
DB2 1.24.0
NR is 4.0.9

In addition the titles on the dashboard widgets got corrupted. See below snapshot. This is happening across multiple widgets - forms / dropdown.

This is now causing serious issues where the dashboard becomes unusable - since user unable to understand the the titles. (esp. on forms with multiple fields)

image
image731×222 6.1 KB

10

This was fixed in latest version.

This is not latest version

11

Great.

I am aware. Reporting it late. The issue cropped up since 1.24.0 and i have not seen anything in RN of 1.24.1 / .2 saying its fixed. So was not sure.

Would you know if its fixed in latest version ? Then i can upgrade and test.

12

You posted a quote from Steve at the start of your reply, saying that it is fixed.

13

Link to release notes for v1.24.1