# Missing (actually hidden) context pop-up in config node editor

**URL:** <https://discourse.nodered.org/t/missing-actually-hidden-context-pop-up-in-config-node-editor/83999>\
**Category:** Developing Nodes\
**Created:** [24 December 2023 00:46 UTC](https://discourse.nodered.org/t/missing-actually-hidden-context-pop-up-in-config-node-editor/83999 "2023-12-24T00:46:51Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![mike](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mike/32/10_2.png) [@mike](https://discourse.nodered.org/u/mike)\
**Post date:** [24 December 2023 00:46 UTC](https://discourse.nodered.org/t/missing-actually-hidden-context-pop-up-in-config-node-editor/83999/1 "2023-12-24T00:46:51Z")

</div>

I notice that the context pop up for config nodes in the bottom right of the editor footer does not appear on my node (and others) unless I manually expand the edit box. Does anyone have a suggestion on how I can expand the default width of my config node edit box so it appears without the user needing to expand it?

This seems like an editor bug (need to research), but it would be good to have a quick work around until it is addressed.

---

<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:** [24 December 2023 00:55 UTC](https://discourse.nodered.org/t/missing-actually-hidden-context-pop-up-in-config-node-editor/83999/2 "2023-12-24T00:55:18Z")

</div>

Not 100% clear. Can you add a gif out screenshots that show us what is happening. Additionally the code from sound that area of you node?

---

<div class="post-metadata">

**Author:** ![mike](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mike/32/10_2.png) [@mike](https://discourse.nodered.org/u/mike)\
**Post date:** [25 December 2023 21:18 UTC](https://discourse.nodered.org/t/missing-actually-hidden-context-pop-up-in-config-node-editor/83999/3 "2023-12-25T21:18:40Z")

</div>

Sure. I found a work around, but here's more info on the general issue.

I made a quick GIF animation showing the TLS config editor used by the HTTP Request node doesn't show the context pop up unless it is resized. This is the same for other config nodes. For me, this led to some users reporting to me that the pop-up was missing in my node.

The MQTT broker config node editor shows the pop up when creating a new config node since it has added tabs.

![Kapture 2023-12-25 at 12.29.02](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/d/7dd92a8b8bfd7580a1440c45a325386b15314c09.gif)

After looking at the HTML for the MQTT node and comparing it with others, I found that default min-width for the editor is too narrow. To work around this, I'm going to set the min-width of one of my rows (e.g. name field) wider as MQTT did. This forces the edit window to be the right size for my node at least.

I think the default min-width should be changed to something wider to ensure it appears on all config nodes.

---

<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:** [25 December 2023 21:48 UTC](https://discourse.nodered.org/t/missing-actually-hidden-context-pop-up-in-config-node-editor/83999/4 "2023-12-25T21:48:46Z")

</div>

Ah, well spotted Mike.

I'm not 100% sure increasing the min-width is the best solution (thinking mobile portrait is tight as it is) but yeah, that is a UI 🪲.

It would be super helpful if you could raise an issue here: [Issues · node-red/node-red · GitHub](https://github.com/node-red/node-red/issues) Please include the info and GIF in the issue with a link back to this post.

---

<div class="post-metadata">

**Author:** ![mike](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mike/32/10_2.png) [@mike](https://discourse.nodered.org/u/mike)\
**Post date:** [25 December 2023 23:19 UTC](https://discourse.nodered.org/t/missing-actually-hidden-context-pop-up-in-config-node-editor/83999/5 "2023-12-25T23:19:48Z")

</div>

Will do. Merry Christmas!

---

<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:** [26 December 2023 09:37 UTC](https://discourse.nodered.org/t/missing-actually-hidden-context-pop-up-in-config-node-editor/83999/6 "2023-12-26T09:37:03Z")

</div>

The same problem can be seen on the influxdb config node.

---

<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:** [26 December 2023 10:35 UTC](https://discourse.nodered.org/t/missing-actually-hidden-context-pop-up-in-config-node-editor/83999/7 "2023-12-26T10:35:34Z")

</div>

I have just realised that it is not coincidence that this has appeared here after I reported the issue against the influxdb node, thinking that it was specific to that node.

---

<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:** [26 December 2023 20:49 UTC](https://discourse.nodered.org/t/missing-actually-hidden-context-pop-up-in-config-node-editor/83999/8 "2023-12-26T20:49:05Z")

</div>

> [@Steve-Mcl](#):
>
> min-width

It would probably be better to set min-width to a var?

---

<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:** [26 December 2023 21:38 UTC](https://discourse.nodered.org/t/missing-actually-hidden-context-pop-up-in-config-node-editor/83999/9 "2023-12-26T21:38:11Z")

</div>

It might be better, if possible, if the 'nodes use this config' string were truncated if not enough room, rather than losing the context field completely.

---

<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:** [28 December 2023 16:02 UTC](https://discourse.nodered.org/t/missing-actually-hidden-context-pop-up-in-config-node-editor/83999/10 "2023-12-28T16:02:00Z")

</div>

I have submitted an issue [Hidden scope dropdown in config node editor · Issue #4497 · node-red/node-red · GitHub](https://github.com/node-red/node-red/issues/4497)

---

<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:** [26 February 2024 16:02 UTC](https://discourse.nodered.org/t/missing-actually-hidden-context-pop-up-in-config-node-editor/83999/11 "2024-02-26T16:02:27Z")

</div>

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