Minor follow up I just noticed on a recent deployment on an Ubuntu machine at my dad's. Version 3.1.4:
This behavior is NOT present.
The behavior is still present on my home Ubuntu machine.
1 Like
I am seeing this exact same behaviour as well. It is very annoying. Has it been logged as a bug?
I don't think it is consistently reproducible. Have you tried accessing Node-RED in an in-private browsing session with no browser extensions? I'm fairly sure that it is a browser and/or OS issue not a Node-RED one, I've had it occasionally in the past myself but I can't remember the reason.
Just tried your suggestions, but alas the issue remains. This is on Windows 10 - Firefox.
But I agree, must be some combo of OS/Browser.
I just tried with Chrome, and am getting the same behaviour! 
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
