FlowFuse / FlowFuse/node-red-dashboard
Feature request: ui-text: label set via msg.ui_update persists and cannot be restored to configured label
- Dominant language
- HTML
- Stars
- 355
- Forks
- 82
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 24
Description
### Current Behavior
Description
I found a reproducible issue with the ui-text widget in Dashboard 2.0.
If the widget label is changed dynamically using msg.ui_update.label, the new label is displayed correctly.
However, after removing the msg.ui_update code again, the widget does not return to the label configured in the editor.
Even the following actions do not restore the configured label:
Partly deploy changed flow or changed nodes
Full Deploy
Browser refresh (Ctrl+F5)
The only way to reset is to restart Node_RED.
This makes iterative development in huge projects unnecessarily cumbersome.
The only workaround I found is:
Copy the ui-text node.
Delete the original node.
Deploy.
The copied node (with a new node ID) again displays the configured label correctly.
This suggests that the runtime label is stored internally and is not reset when the widget configuration changes.
### Steps to reproduce
Create a ui-text widget with a configured label (e.g. "Original Label").
Send:
msg.ui_update = {
label: "Dynamic Label"
};
return msg;
Verify that the widget now shows "Dynamic Label".
Remove the code that sends msg.ui_update.label.
Deploy the flow (Full Deploy).
Expected behaviour
The widget should display the label configured in the editor again.
### Actual behaviour
The last dynamically assigned label remains visible permanently.
### Workaround
Creating a new ui-text node (copy/delete original) restores the expected behaviour.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the ui-text widget behavior with msg.ui_update.label, then trace how the widget applies that runtime label during deployment and configuration updates. Done means removing the dynamic update and deploying again restores the label configured in the editor without restarting Node-RED or recreating the node.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100