Bug? Disable button on Debug node

[phreed]

When I press the enable button on the debug node I get unexpected behaviour.
The enable/disable is toggled as expected but the blue dot comes on.
The blue dot indicates that the node needs to be deployed.
However, the behaviour toggles without the deploy.

This is different than the behaviour on the inject node.
When the trigger button is pushed on the inject node the behaviour is triggered but no blue dot appears.

I have replicated this in Node-RED v3.1.9 & 3.1.14

[joepavitt]

I also noticed this recently when recording a tutorial, running v4.x - thought it was odd at the time, but forgot to return to it.

[GogoVega]

Seems not a bug:

[phreed]

Just because it was intentional does not mean it is not a bug.
Explain how the behaviour makes sense.

[E1cid]

The disabling of the debug is a change to the flow json in the editor, if you refresh the page it will reenable, unless you deploy, hence the blue dot to show you that the editor/node has a change that you may want to save.
Pressing the inject button sends a request/msg to the server running the flows but nothing is changed on the editor, hence no blue dot.

[phreed]

I guess the issue is that the blue dot is doing double duty.
It indicates that

• the changes in the editor are not persistent.
• the changes have not been propagated to the engine running the flows.

The former being the official significance, the later a happy coincidence.
Could an alternate colour indicate the difference?