# Open comment node in new window

**URL:** <https://discourse.nodered.org/t/open-comment-node-in-new-window/98198>\
**Category:** Feature Requests\
**Created:** [18 July 2025 11:01 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198 "2025-07-18T11:01:49Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![duaw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/duaw/32/20970_2.png) [@duaw](https://discourse.nodered.org/u/duaw)\
**Post date:** [18 July 2025 11:01 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198/1 "2025-07-18T11:01:49Z")

</div>

Hi there!

I document within NR using comment nodes. So far, so good.

When I implement something I _close_ my comment node in oder to _open_ (and edit) another node.

I find no way to keep the contents of a comment node visible while juggling with another node.

I can open the debug _tab_ in a new window. I would be great to keep a comment _node_ open while editing othe nodes. That would be super helpful with my weak short term memory.

Or do I miss here something and I can do that already? If so, enlighten me, please.

If not: Do you think this is a good idea and can, should be implemented?

Or: How do you manage to keep information from your comments in your head after you close the comment node …

Cheers, Uwe

---

<div class="post-metadata">

**Author:** ![smanjunath211](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/smanjunath211/32/95742_2.png) [@smanjunath211](https://discourse.nodered.org/u/smanjunath211)\
**Post date:** [18 July 2025 12:02 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198/2 "2025-07-18T12:02:00Z")

</div>

> [@duaw](#):
>
> How do you manage to keep information from your comments

i usually open a notepad and do alt+tab between NR and Notepad or keep both windows cascaded. later on copy all the contents from notepad into comment node .

---

<div class="post-metadata">

**Author:** ![duaw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/duaw/32/20970_2.png) [@duaw](https://discourse.nodered.org/u/duaw)\
**Post date:** [18 July 2025 12:34 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198/3 "2025-07-18T12:34:40Z")

</div>

Yeah, this is a possibility However, it looks … clumsy, like a workaround, not smooth. The tool (NR) forces you to do something that could be handled by the tool itself.

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [18 July 2025 12:52 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198/4 "2025-07-18T12:52:51Z")

</div>

> [@duaw](#):
>
> However, it looks … clumsy, like a workaround, not smooth.

It is! I built myself a scratchpad node that gives me empty text fields where I can paste stuff temporarily (or save it in the flow). The node or better said plugin, lives in the sidebar so that it never closes.

I might publish it, I've only use it privately because I haven't seen a broader need and also because I didn't want to write documentation for it!

You can try it out over at the [serverless Node-RED](https://cdn.flowhub.org), it's included in that.

 ![Screenshot 2025-07-18 at 14.47.46](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/f/5f57f9efa7ae59cd3f81eb98ca2bb261c5a0084c.png)

---

<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 July 2025 12:56 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198/5 "2025-07-18T12:56:59Z")

</div>

> [@duaw](#):
>
> I can open the debug _tab_ in a new window.  
> ...  
> something that could be handled by the tool itself.

Are you suggesting that the debug node config dialog should have a similar "Open in new window" option?

What about the Description tab of the config dialog for all nodes?

These browser popups would be read-only?

---

<div class="post-metadata">

**Author:** ![duaw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/duaw/32/20970_2.png) [@duaw](https://discourse.nodered.org/u/duaw)\
**Post date:** [18 July 2025 13:24 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198/6 "2025-07-18T13:24:53Z")

</div>

I talk about a requirement (feature):

- The "properties" of one (or more) comment node(s) shall be visible (as rendered markup) while editing another node.

I don't know anything about how to implement this "visibiity". One first, naive idea was to implement it like the debug tab which can be displayed in a new window, that is: _show the rendered markup of a comment node in a new browser window_. Perhaps just one comment node in just one new window. Another one in another window, if necessary. When done, close the browser windows with the comment's rendered markup.

I am aware that one can run into problems here: does it fit to NR approach and its UI "rules"? What about showning a comment while editing exactly this comment … ?

I cannot say that if would be wise to add the option "Open in new window" to the whole "Info" tab. I think not. But I think it might be nice to have rendered markup of comments like sticky notes available on the screen (each in a new browser window), just like the debug tab.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [18 July 2025 14:08 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198/7 "2025-07-18T14:08:31Z")

</div>

Perhaps the Info sidebar could be made to tear off. That would be a start at least. It renders the comments for a node selected in the sidebar.

---

<div class="post-metadata">

**Author:** ![LosinIt](https://avatars.discourse-cdn.com/v4/letter/l/439d5e/32.png) [@LosinIt](https://discourse.nodered.org/u/LosinIt)\
**Post date:** [18 July 2025 15:44 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198/8 "2025-07-18T15:44:03Z")

</div>

I don't think it clumsy at all. I do this very thing for _most_ of my sysadmin tasks so it is natural to do the same in NR.

If this gets implemented I hope I can disable it!

---

<div class="post-metadata">

**Author:** ![duaw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/duaw/32/20970_2.png) [@duaw](https://discourse.nodered.org/u/duaw)\
**Post date:** [19 July 2025 09:12 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198/9 "2025-07-19T09:12:50Z")

</div>

Users are different. Like the debug sidebar tab, you should be free to use the feature to detach it and open a new browser window ... or not.

---

<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:** [19 July 2025 13:45 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198/10 "2025-07-19T13:45:35Z")

</div>

> [@duaw](#):
>
> you should be free to use the feature to detach it and open a new browser window ... or not.

I agree. It would be a nice enhancement to duplicate the debug sidebar detach button for comment nodes and node descriptions, if it's not a huge task.

My procedure is to copy and paste into Notepad or a window running vi, so I wouldn't personally use it though 🫠

---

<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:** [19 July 2025 14:18 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198/11 "2025-07-19T14:18:26Z")

</div>

I think the request is not just to detach it, but to keep it open on the original node whilst editing other nodes.

---

<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:** [19 July 2025 14:32 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198/12 "2025-07-19T14:32:56Z")

</div>

I've often wished I could keep the sidebar help for one node open while I'm editing another. Another place this feature might be handy?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [19 July 2025 16:04 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198/13 "2025-07-19T16:04:03Z")

</div>

> [@jbudd](#):
>
> I've often wished I could keep the sidebar help for one node open while I'm editing another

while the help panel does update when ever you edit a different node, you can easily change/view help of any node while editing a different one.

![chrome_qqgRoq9xBm](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/e/5ea093df817c1e0f00d8484e2375bcaf81eab69f.gif)

---

<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:** [19 July 2025 19:47 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198/14 "2025-07-19T19:47:28Z")

</div>

> [@Steve-Mcl](#):
>
> you can easily change/view help of any node while editing a different one.

Though that is just the generic help for a node type isn't it? Not the description that you may have added to a particular instance of a node.

---

<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:** [19 July 2025 19:56 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198/15 "2025-07-19T19:56:40Z")

</div>

> [@Colin](#):
>
> Though that is just the generic help for a node type isn't it?

Blame me. I was just thinking of other places where it _might_ be valuable to have something in a separate browser window.

- Comment node contents
- Debug node output (and any new/third party debug nodes)
- Node description
- Node help

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [17 September 2025 19:57 UTC](https://discourse.nodered.org/t/open-comment-node-in-new-window/98198/16 "2025-09-17T19:57:31Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.