# Slight \*bug\* with \`change\` node and the \`add\` button

**URL:** https://discourse.nodered.org/t/slight-bug-with-change-node-and-the-add-button/19799
**Category:** Feature Requests
**Created:** [1 January 2020 20:21 UTC](https://discourse.nodered.org/t/slight-bug-with-change-node-and-the-add-button/19799 "2020-01-01T20:21:13Z")
**Posts on this page:** 8
**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: [1 January 2020 20:21 UTC](https://discourse.nodered.org/t/slight-bug-with-change-node-and-the-add-button/19799/1 "2020-01-01T20:21:13Z")

</div>

I am starting to use the `change` node a bit more for changing messages.

But time and time again, I am needing to add a second field to the message body.  
(Say topic)

The `add` (bottom left of the window) is now obscured by the `enabled` button.  
(See picture)

Could the size of the scroll window be reduced so the `add` is above the `enabled` button?

 ![Screenshot from 2020-01-02 07-16-43](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/d/dfbb14c0783d6a8593c6a47c504e5cd429a2ceaf.png)

Just asking.

---

<div class="post-metadata">

### Author: ![afelix](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/afelix/32/9743_2.png) [@afelix](https://discourse.nodered.org/u/afelix)
#### Post date: [1 January 2020 20:29 UTC](https://discourse.nodered.org/t/slight-bug-with-change-node-and-the-add-button/19799/2 "2020-01-01T20:29:09Z")

</div>

What browser are you seeing this on? It looks like a styling bug in the CSS somewhere, potentially dealing with resolution somewhere to me. I use the change node like this on a daily base and it’s the first time seeing this. If you look closely the “delete field” button is also partially hidden.

Platform node red is installed on?  
Version of node-res?  
Platform you’re viewing this on?  
What browser plus version of it?  
Any special situations like are you using a browser on the device that runs node red through VNC?  
What’s the screen resolution of the device running the browser?

As for a workaround, you’re dealing with two vertical scrollbars. One in the inner area that shows the rules (set/delete/... with editor for each), and an outer one for the node configuration field. To get so far down, put your mouse cursor to the top of the node config form (name field for example), then scroll down using your mouse wheel or equivalent. That moves the outer scrollbar instead.

---

<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: [1 January 2020 20:33 UTC](https://discourse.nodered.org/t/slight-bug-with-change-node-and-the-add-button/19799/3 "2020-01-01T20:33:57Z")

</div>

Direct access all local.

Ubuntu 18.04 LTS  
NR 1.0.3  
FF  
Plugins....  
AdsBlock  
ClearFlashCookies  
FlagFox  
Mooltipass  
SaveImagetoDownload  
SimpleTab Rename

---

<div class="post-metadata">

### Author: ![afelix](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/afelix/32/9743_2.png) [@afelix](https://discourse.nodered.org/u/afelix)
#### Post date: [1 January 2020 20:53 UTC](https://discourse.nodered.org/t/slight-bug-with-change-node-and-the-add-button/19799/4 "2020-01-01T20:53:33Z")

</div>

Which firefox version would that be? Is likely relevant to reproduce it. Also screen resolution as it appears to fit the content to the limited space available and that’s why the double scroll bar happens. I might try to reproduce it tomorrow in a VM, if the resolution falls within common sizes

---

<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: [1 January 2020 21:00 UTC](https://discourse.nodered.org/t/slight-bug-with-change-node-and-the-add-button/19799/5 "2020-01-01T21:00:02Z")

</div>

70.1 (The latest?) 64bit

Resolution?

I am guessing it is something like: 1368 x 786?

I don't know these new resolutions.  
It is a HDMI monitor and _it works out what is needed/being used_

As things are "plug and play" (though I am not using windows) I have never really set the resolution.

How do I find it?  
(P.S. Going off line very soon. The day has now started for everyone else and so I need to now get going.)

---

<div class="post-metadata">

### Author: ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [1 January 2020 21:23 UTC](https://discourse.nodered.org/t/slight-bug-with-change-node-and-the-add-button/19799/6 "2020-01-01T21:23:35Z")

</div>

The min-height is probably set a bit too high for that node on "low" res screens - (and likewise the switch node). We can adjust it.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [1 January 2020 21:32 UTC](https://discourse.nodered.org/t/slight-bug-with-change-node-and-the-add-button/19799/7 "2020-01-01T21:32:40Z")

</div>

> [@Trying\_to\_learn](#):
>
> It is a HDMI monitor and _it works out what is needed/being used_  
> As things are "plug and play" (though I am not using windows) I have never really set the resolution.  
> How do I find it?

In Ubuntu standard setup it is Settings \> Devices \> Screen Display

---

<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: [2 January 2020 02:27 UTC](https://discourse.nodered.org/t/slight-bug-with-change-node-and-the-add-button/19799/8 "2020-01-02T02:27:13Z")

</div>

1360 x 768 resolution.

To me that is high.

1024x768 used to be high res. I never really got above that until I got into Ubunto and RasPis with their HDMI outputs.

That is what it started as and so I am happy with that.

@dceejay  
I am only stating what I have, and the problem it is _causing_.  
If it is not fixable, ok. If it can be _adjusted_: even better.
