# \[req\] Enable / Disable TABs from search list (v3.2+)

**URL:** https://discourse.nodered.org/t/req-enable-disable-tabs-from-search-list-v3-2/84173
**Category:** Feature Requests
**Created:** [1 January 2024 10:50 UTC](https://discourse.nodered.org/t/req-enable-disable-tabs-from-search-list-v3-2/84173 "2024-01-01T10:50:23Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![PizzaProgram](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/pizzaprogram/32/19431_2.png) [@PizzaProgram](https://discourse.nodered.org/u/PizzaProgram)
#### Post date: [1 January 2024 10:50 UTC](https://discourse.nodered.org/t/req-enable-disable-tabs-from-search-list-v3-2/84173/1 "2024-01-01T10:50:23Z")

</div>

1. I'd like to request an easier method to Disable / Re-enable TABs from the list.
2. Maybe the filters could be enhanced too, (on the top-right corner,) to show only enabled / disabled...
3. Also a "locked" / "unlock" button would be great.

 ![kép](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/f/4fab52d07d8af81447abdf073d9f59dd0ab76dc6.png)

If that's not possible, at least small icons should be visible to see:

- which TAB is disabled,
- which is locked
- which is changed and need to be deployed

# Size:

- Also this very useful drop-down-list should reach the bottom, not just half of the screen.  
(Set height to max)

## The reason:

I've just realized how much time it takes to disable all tabs one by one, if trying to test a new node which would conflict with the current one.  
The base-concept of NR is to use many TABs = flows, to be organized more nicely, not to put many nodes on a few Tabs.  
But scrolling tabs horizontally to find which tab needs to be enabled / disabled is currently not so practical.

---

<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: [1 January 2024 12:02 UTC](https://discourse.nodered.org/t/req-enable-disable-tabs-from-search-list-v3-2/84173/2 "2024-01-01T12:02:46Z")

</div>

And if the enhancement gods were to look on us kindly after a successful year, the ability to GROUP tabs would also be SUPER NICE! 🕶

---

<div class="post-metadata">

### Author: ![ralphwetzel](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ralphwetzel/32/53713_2.png) [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)
#### Post date: [1 January 2024 12:40 UTC](https://discourse.nodered.org/t/req-enable-disable-tabs-from-search-list-v3-2/84173/3 "2024-01-01T12:40:57Z")

</div>

> [@TotallyInformation](#):
>
> GROUP tabs

Only in this list or as a general feature? How would/could/should that look like?  
What could/should be the key for grouping? Any what's the benefit at all... ?

---

<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: [1 January 2024 13:36 UTC](https://discourse.nodered.org/t/req-enable-disable-tabs-from-search-list-v3-2/84173/4 "2024-01-01T13:36:36Z")

</div>

> [@ralphwetzel](#):
>
> Only in this list or as a general feature?

Well both I suppose. 🙂

> [@ralphwetzel](#):
>
> How would/could/should that look like?

For the list, that would be a normal tree layout. For the tabs themselves, It would either need to add another row above (which I suspect most people wouldn't like) or something similar to the way that grouped tags work in the Edge browser:

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/c/8c0a40e97b2e5e3924a700b6cd5d3d58ac67bfcc.png)

A "pill" is shown before the group with a colour and a narrow line of the same colour above the grouped tabs. In edge, the group can be collapsed simply by clicking on the pill.

> [@ralphwetzel](#):
>
> What could/should be the key for grouping?

Would need a new key, set manually when needed

> [@ralphwetzel](#):
>
> Any what's the benefit at all... ?

This really enhances usability if you have a lot of tabs. At the moment, you can only hide tabs and then you have to unhide them if you want to access them. With grouping, you only need to click on the pill to collapse/expand the group.

This could also be integrated with PizzaProgram's suggestion so that you could dis-/en-able a complete group of tabs.

---

<div class="post-metadata">

### Author: ![PizzaProgram](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/pizzaprogram/32/19431_2.png) [@PizzaProgram](https://discourse.nodered.org/u/PizzaProgram)
#### Post date: [1 January 2024 17:52 UTC](https://discourse.nodered.org/t/req-enable-disable-tabs-from-search-list-v3-2/84173/5 "2024-01-01T17:52:07Z")

</div>

If this feature is really considered,  
than Instead of "Tab-group", an other naming would be better, so it won't be mixed with node-grouping, like:

> Tab-collection / Collections

But I think it would be even better to use:

> TAB-TAGs

This way you could add multiple Tags to Tabs, and disable / enable ... or hide / show them by those.

_I always prefer TAGs, because it does not make to much more effort to program, but it increasing the usability hugely._

For example:

- disable all "summer-flows" TAG
- hide all "test" TAG

A little similar to Wekan .

 ![kép](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/b/1b7a8ec17c77206539c21ee9df372ca4425f2e08.png)

PS: @TotallyInformation it would have been nice, if you open your OWN topic for this, and do not mix mine with this request.  
Maybe ask a @moderator to separate the 2 topics please?

---

<div class="post-metadata">

### Author: ![ralphwetzel](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ralphwetzel/32/53713_2.png) [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)
#### Post date: [1 January 2024 20:10 UTC](https://discourse.nodered.org/t/req-enable-disable-tabs-from-search-list-v3-2/84173/6 "2024-01-01T20:10:00Z")

</div>

I just discovered that this feature / style made its way as well into the Chrome browser.

---

<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: [1 January 2024 20:25 UTC](https://discourse.nodered.org/t/req-enable-disable-tabs-from-search-list-v3-2/84173/7 "2024-01-01T20:25:01Z")

</div>

Yes, all of the Chromium-based browsers should have something similar.

---

<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: [1 March 2024 20:25 UTC](https://discourse.nodered.org/t/req-enable-disable-tabs-from-search-list-v3-2/84173/8 "2024-03-01T20:25:53Z")

</div>

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