Hide editor tabs without disabling them

I don't know if this option exists in the editor.

It would be nice if you could do the same thing that happens with the subflows and you could hide the tabs when they are not being edited.

If you hide them from the editor - then how would you get them back to edit them ? They have to exist in the editor.

Why? you can search it with the search buttom (tab).

One of the common pieces of feedback we got in the developer survey last year was for there to be better management of the tabs in the editor - especially for users with lots of tabs.

We added the search box in 0.20 (maybe... or was it 1.0...) to help with the navigation but there's more to do. Before we added that search box, the idea of closing regular flow tabs was never going to happen.

With the search box, then maybe it isn't a completely off-limits idea. But it does need some careful consideration. I'm not sure the search box alone is sufficient for a user to know instinctively what they have got available to them.

There are some other ideas kicking around to help the general navigation of the workspace and to increase visibility of what is there. As those ideas progress, then maybe the idea of closing editor tabs can be revisited.

I would hope this is a per edit session thing rather than in the flow. I would hate to be sent a flow that looked innocent but had hidden tabs executing who knows what - with no way for me to find them as I don't happen to know the name...

1 Like

I like (perhaps accept is a better word) what the browsers do with tabs - shrink them as the number of tabs grow.

Failing that, then perhaps an option to show an fa icon only?

Another option might be, a drop-down list when the tabs start to overflow?

@dceejay good point on importing.

Sorry I can't help with any actual coding (I'm not great with presentation / CSS) but hope there is some food for thought as you guys explore this.

@dceejay Good one. But if you import a flow with 20 tab, and one do a "abnormal" executing it will do as you see the tab or no. Maybe a number with the hidden tabs near the menu can help with a import.

@Steve-Mcl shrink tabs like browser do, finish with a pixel tab if you open more tabs. Drop-down list with a option of pin tab maybe could be good one.

We do shrink the tabs, but as tabs don't have individual icons then we need to keep some of the label visible.. which limits the minimum they can be. We could add the option to give tabs custom icons.. don't think that has been considered before.

Some browsers don't force all tabs to be visible at once. Firefox (iirc) scrolls them in the same way we do.

We used to force them all on screen and they got pixel small. Users complained it was unusable in that state - and they were right. Hence the current implementation.

Already got that.

1 Like

Oh. Of course the search box tab list.

@ElGranLoky - if I import a flow via cut/paste then I can visually inspect the flow before hitting deploy... (ie not running) - but only if I can see all the tabs... One of the main features of Node-RED is this ability as it allows folk here on the forum to help others by inspecting their flows quickly without running them. I'd hate for us to lose that.

As someone who has a ridiculous number of tabs in my Win10 instance (I just test flows out and never delete them) - maybe just set a max limit of 10 and charge ££££ for Node-REDPro if users want more :slight_smile:

1 Like

@dceejay Yes, I also think that helping others is an important part of nodered, and that it has to be something simple to do. But I don't think it's incompatible with hiding tabs in the editor. For example:

1.- When importing enable an option to disable all hidden tabs and make them visible, or keep importing hidden tabs.
2.- Show the number of hidden tabs next to the drop-down menu once imported, or always.

When I have more than 10 tabs open it is a nuisance to move between them, especially when 3 or 4 I almost never touch them for having them finished.

I think when importing they should always be shown. If you then chose to hide them that is up to you.. So as I said, it should be held in the editor/browser state and not in the flow file.

Icons and perhaps colors :+1: “a picture can sometimes say more than 1000 words” And most of us are so bad in naming things - especially I am.

And a second line if you open subflows would be great too.

Only some suggestions.

In terms of scalability with many flow tabs, I would like to revisit the idea of a vertical flow list in the sidebar. :slightly_smiling_face:

Some related discussions about this topic:


Thank you for linking to all the previous conversations. As I said in my reply right at the start of this topic, there are a number of ideas being kicked around already in this area. And as I said, we can consider the ability to close tabs once some of those ideas are more fully formed and we are able to address the various usability concerns this would introduce.