Discussion - Set Aside Tabs and Warn on Close

Elliot Kirk 

Here's my take on Set Tabs Aside.

I loved that the feature existed. It was a refreshing feeling to use it. I felt more free when I had it, that I could put things on hold. I was more agile, that I could interrupt when I want (in a good sense) whatever, and have a fresh/undistracted view of this immediate, more important task.

Now, in its absence, I feel chained down to my open tabs. They pose detriment against a context switch. Even if there are weeks until the time I will use many of my tabs, I cannot set them aside, and they surely diminish my focus when they are 9/10 of my active tabs.

Think of a CPU without interrupts. That's how it's kind of like to not have the Set Tabs Aside.

Suggestions for improvement:

1. Please auto-close the single empty new tab page, when the user retrieves a stack of tabs set aside: Setting tabs aside, and retrieving another stack was a common workflow of mine. However, every time you did this, you'd have an empty new tab page, which was annoying. Same thing happened also when you'd open a fresh new browser, and retrieve a stack.
2. A means to conjoin the currently open tabs with a stack of tabs set aside. I.e. stack tabs aside INTO some other set of tabs set aside.

Really, this was the number 1 feature I was advertising people back in old Edge times. I was making Mac people envious with it...