BUG: Opening the switch node has strange behavior

When I open the switch node I have strange behavior:


Works on Chrome but not on Safari (v17.1)
Node-RED v3.1.1

This happens to me - but I wouldn't call it a bug (more the window going crazy for a few s) - as its not causing any problems (at least for me), maybe a quirk with Safari

and I'm using 3.1.0.

wait - is it closing also?

Out of interest, if you fully refresh and the first thing you do is open the change node, does it still happen?

Ps: Safari is the new...

Couldn't help your self eh!? :wink:

1 Like

Perhaps, but he is right. Not sure what Apple are thinking but it is a bit embarrassing. I have my sneaking suspicion that they stay out of step with the current W3C standards:

a) because they are Apple who believe that they make the sun shine.
b) because they hate Google who tend to drive a lot of W3C standards.

1 Like

Yes, this happens too

Fun fact!

Apple have enterprise contracts with Google (the last time I read about the setup), and the last I knew - iCloud storage is hosted on Google Servers.

Me -> My Encryption Key -> iCloud (Apple) -> Apples master Google Storage encryption Key -> Google

Google and...

This story is going into a tailspin :joy:

1 Like

To get back on track

does the editor dialog close on its own?
I get the screen fit - but nothing closes on its own (3.1.0)

No it's the GIF loop, the editor still open

1 Like

In that case, I get this crazy screen activity on 3.1.0 - but its not really causing me any issues

If this can be recreated then please raise an issue.

@GogoVega I'm running on Mac mini M1 with Ventura 13.6 and Safari 16.6.

Updated to NR 3.1.1 and see no issue with opening the switch node.

What is all the background in your image? Have you got any contrib nodes installed?
Are you running different dashboard node or have more than one installed?
Have you tried clearing the browser cache?

Thanks Paul.

This looks and smells like a safari v17.1 regression.

Ref: [BUG]: Safari: Opening the switch node has strange behavior · Issue #4463 · node-red/node-red · GitHub

I tested with a new basic installation and clearing the Safari cache, I still have this strange behavior

Because, you are still using Safari 17.1 right?

This certainly appears to be a Safari regression introduced somewhere between 16.x and 17.1

Why do I think that?
  • it was never reported for Node-RED 3.1.0 but you are seeing this on Node-RED 3.1.0 AND 3.1.1
  • @zenofmud, who has Safari 16.x has confirmed this does not happen on either Node-RED 3.1.0 OR 3.1.1
  • The deafening silence from every other non-safari user

It's very likely, unfortunately I can't test on an earlier version of Safari.

My only reluctance is why only this node?

Good question indeed.

I have seen this before. I think when something in a node setup is broken or slow to initialise (I couldn't pin it down, so never debugged it). So in fairness to all, it might be a letent issue illuminated for the world to see, indirectly by whatever is going on with safari.

It might be that the editor code for that node is not isolated in an IIFE. I've previously seen cases where that causes unintended side-effects. Not really that surprising given the sheer volume of shared code that is loaded in your average Node-RED installation. :slight_smile:

Possible but the switch node is isolated