# SWITCH node - bug?

**URL:** <https://discourse.nodered.org/t/switch-node-bug/16058>\
**Category:** General\
**Created:** [29 September 2019 13:37 UTC](https://discourse.nodered.org/t/switch-node-bug/16058 "2019-09-29T13:37:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [29 September 2019 13:37 UTC](https://discourse.nodered.org/t/switch-node-bug/16058/1 "2019-09-29T13:37:39Z")

</div>

(Ok, no more "bug" section)

I am using a few `switch` nodes.

Alas they are BIG. Well, just now I am up to 14 outputs.

Recently when I open them, scrolling inside them is painful.

From memory the list starts at the bottom, but either way:  
I want to get to the other end.  
I start to scroll with the MMB.  
So, I scroll and get to the _other end_ of the list.  
As soon as I stop, it jumps back to the original end of the list.

This happens for about 4 tries then it finally _obeys_ me and stays scrolled at the other end.

Bug?

It is not really practical sending in screen shots. It is a dynamic thing that won't really be seen with pictures.

---

<div class="post-metadata">

**Author:** ![Andrei](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/andrei/32/10446_2.png) [@Andrei](https://discourse.nodered.org/u/Andrei)\
**Post date:** [29 September 2019 13:53 UTC](https://discourse.nodered.org/t/switch-node-bug/16058/2 "2019-09-29T13:53:47Z")

</div>

There was a nice initiative few weeks ago to improve the rendering of the switch node.  
I guess this improvement is already available in the latest release of Node-RED. At least I don´t perceive slowness in a testing switch with 21 outputs. Also I never noticed the behavior you mentioned in your post. This leads me to ask you the very well known question: in which version of Node-RED you are perceiving the issue ?

> <https://github.com/node-red/node-red/pull/2258>

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [29 September 2019 14:00 UTC](https://discourse.nodered.org/t/switch-node-bug/16058/3 "2019-09-29T14:00:31Z")

</div>

NR 0.20.5  
Dashboard 2.16.3 - though I don't think that is relevant.  
And node = 8.12.0 (just in case)

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [29 September 2019 14:08 UTC](https://discourse.nodered.org/t/switch-node-bug/16058/4 "2019-09-29T14:08:26Z")

</div>

Oh, sorry, this is another "problem"

When I want to add another _switch_.

I see this:

 ![Screenshot%20from%202019-09-30%2000-06-59](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/8/8b0e041ec9c304f595dccb6cec0ab2a3e00a09c0.png)

#15.  
But I can't get to it.

I have to close the node and re-enter it.

---

<div class="post-metadata">

**Author:** ![Andrei](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/andrei/32/10446_2.png) [@Andrei](https://discourse.nodered.org/u/Andrei)\
**Post date:** [29 September 2019 14:10 UTC](https://discourse.nodered.org/t/switch-node-bug/16058/5 "2019-09-29T14:10:46Z")

</div>

Never experienced that. May you perhaps do a quick testing using Chrome instead of Firefox ?

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [29 September 2019 14:12 UTC](https://discourse.nodered.org/t/switch-node-bug/16058/6 "2019-09-29T14:12:31Z")

</div>

OK, shall try to remember.

Still doing massive re-work on a lot of flows.

All flows are password protected and I don't have the passwords handy.  
Sorry.