Forum Discussion
Discussion - Set Aside Tabs and Warn on Close
Set tabs aside is my favorite feature in the old Edge. I use it to set aside tabs related to tasks or research I need to get back to later, which makes it easier to manage tabs I working with at the moment and frees up the computer's resources.
I like where the button is in the old Edge, and I think that's the only sensible place to put it. You could add an option to remove it for people who are bothered by it.
The improvements I would like to see are:
- ability to name groups of tabs set aside
- sync of tabs set aside across devices
I would also like the option to reopen a closed window when working with multiple windows. If you have that, and the browser is set to continue where you left off on startup, then there is no need for the prompt asking if you want to close all tabs when you close a window. But I think you should still add it as an option for people who want it.
- MarinM Elliot Kirk I actually had the same thought. I'd even suggest having a button to dismiss, and then a check box for Don't Show This Notice Again.
JaturnMicrosoft
Yes, Set Aside was my favorite feature of old Edges as well and I share the same sentiments as others on this thread concerning button placement, renaming Set Aside groups and, possibly, combining collections without loosing the benefits/ease of the Set Aside features from old Edge. I would suggest 2 more things.
1. The ability to permanently store Set Aside tabs as favorites tabbed groups or, vice verse, open favorite groups as a group within Set Aside tabs. If we combine it with collections then we would have those features available (Sharing ...etc).
2. Consider adding Set Aside tabs to windows timeline.
Note: There was a performance issue with the old Edge Set Aside tab that I want to ensure is fixed in the new feature. The issue was, if you previously set aside "lots:" of tab groups, the browser begin to exhibit performance degradation when you click to open the Set Aside frame. It would take a long time to open and the CPU would jump to 100% percent. it appear that the underlying storage framework that keep track of all the groups wasn't optimized for extensive use of the feature.
