# Clicking the far right of the editor window closes node config

**URL:** <https://discourse.nodered.org/t/clicking-the-far-right-of-the-editor-window-closes-node-config/102181>\
**Category:** General\
**Created:** [18 November 2026 11:14 UTC](https://discourse.nodered.org/t/clicking-the-far-right-of-the-editor-window-closes-node-config/102181 "2026-11-18T11:14:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [18 November 2026 11:14 UTC](https://discourse.nodered.org/t/clicking-the-far-right-of-the-editor-window-closes-node-config/102181/1 "2026-11-18T11:14:19Z")

</div>

The right sidebar has a few pixels above, below and to it's right which "belong to" the editor background.

I understand that it was a conscious decision to have this sidebar floating - I think the reason was "to maximise the editor screen space"?

However it is **infuriating** when switching back and forth between the Monaco editor and debug panel to **accidentally click just to the right of the debug scrollbar and the editor closes.**

Whatever the value of the gap above and below the sidebar, surely the space to the right of it would be more useful on the left, ie actually part of the main visible desktop?  
But if the layout is set in stone, can the click action be disabled in this dead space to the right?

Edit:  
Here is a screen capture with the greyed out background reddened for easy visibility. It's the very far right that is a pain.

Seen on Node-red 5.0.9, Firefox.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/a/5a5da9ecfff8039c40536caaf99ac1a9ea873408.png)

---

<div class="post-metadata">

**Author:** ![krotname](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krotname/32/108839_2.png) [@krotname](https://discourse.nodered.org/u/krotname)\
**Post date:** [18 November 2026 17:05 UTC](https://discourse.nodered.org/t/clicking-the-far-right-of-the-editor-window-closes-node-config/102181/2 "2026-11-18T17:05:00Z")

</div>

There is a concrete code path for this in 5.0.9: [tray.js, lines 234–240](https://github.com/node-red/node-red/blob/5.0.9/packages/node_modules/%40node-red/editor-client/src/js/ui/tray.js#L234-L240) binds a click on `#red-ui-editor-shade` to the tray's primary button. For the normal node editor, that primary button is **Done** ([editor.js](https://github.com/node-red/node-red/blob/5.0.9/packages/node_modules/%40node-red/editor-client/src/js/ui/editor.js#L1163-L1169)).

That makes the gap more than a dismissal problem: a click there can accept the edit. Your screenshot already identifies the hit area. A useful regression test for a layout fix would be to change a field, click that strip, and check whether the edit is accepted, including after resizing the sidebar. Preventing that strip from receiving the editor-shade click would preserve the intended behavior on the actual workspace background.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [18 November 2026 17:54 UTC](https://discourse.nodered.org/t/clicking-the-far-right-of-the-editor-window-closes-node-config/102181/3 "2026-11-18T17:54:01Z")

</div>

@jbudd thanks for the feedback - not something that had been highlighted before. I'll raise an issue to capture it and we can consider how to reduce your frustration.

@krotname your reply reads very much like an AI response that doesn't actually add value to the conversation. You are confirming what jbudd says without contributing anything to help address it.

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [18 November 2026 17:55 UTC](https://discourse.nodered.org/t/clicking-the-far-right-of-the-editor-window-closes-node-config/102181/4 "2026-11-18T17:55:28Z")

</div>

> [@krotname](#):
>
> a click there can accept the edit.

Well that is true but it alleviates the problem rather than adding to it imho.

I did test if the changes already made were saved and they are. I'm ok with that, on the rare occasion when i made a change but don't want to save it there is Ctrl z.

Yoh can probably see I use an editor CSS file to make the scrollbars more visible. I feel that there ought to be a CSS way to fix this issue but so far I have not discovered it.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [18 November 2026 17:58 UTC](https://discourse.nodered.org/t/clicking-the-far-right-of-the-editor-window-closes-node-config/102181/5 "2026-11-18T17:58:06Z")

</div>

I have raised [Clicking the far right of the editor window closes node config · Issue #6115 · node-red/node-red · GitHub](https://github.com/node-red/node-red/issues/6115)
