Allow variable width flow tabs (UI feature request) #83
Replies: 2 comments
-
Hi @jpravetz Thanks for the request. Over the history of the project we've tried a few different approaches for the tabs, and had plenty of feedback from the community with each iteration. We did at one point do as you describe; shrink the tabs, but we found you needed a reasonable minimum size otherwise it became hard to distinguish - at which point, the benefit of shrinking was a bit lost. Unlike browsers, we don't have favicons to help identify the different tabs when they are shrunk down. I'll also note each browser has a slightly different behaviour. Chrome appears to just squash everything into the visible tab bar. Firefox shrinks but then overflows to making it scrollable. So, whilst I won't claim what we have is perfect, it does come as the result of some amount of iteration. |
Beta Was this translation helpful? Give feedback.
-
I totally get your points. You've definitely been listening to users longer than I've been a user :-). In reality your Thanks for the response. Node-RED is a really nice tool with already great UI. |
Beta Was this translation helpful? Give feedback.
-
This is a nice to have feature request.
If you have a lot of flows/subflows the number of tabs open will exceed the space and you must scroll to see the hidden tabs. Very conveniently, a mouse scroll wheel can be used for this.
However, it would be nice if the tabs were more like in a browser (eg. Firefox), where they squish to a narrower width, so that they all fit, up to the point where the tabs are too narrow (just like browsers implement). Alternatively you can do like in VSCode and make variable width tabs, dependent on their titles. My opinion is that the browser-style implementation, where all tabs are the same width, is better. But either solution would be an improvement.
These are the tabs I am referring too (in case there is confusion):
Beta Was this translation helpful? Give feedback.
All reactions