Forum Discussion
Elliot Kirk
Jan 21, 2020Former Employee
Discussion - Set Aside Tabs and Warn on Close
Hi Insiders, we have received a lot of feedback about how you would like to close your tabs with the option of easily finding and reopening them later as you move between different workflows. Specifi...
MarinM
Jan 27, 2020Iron Contributor
I just had an idea for how you could appease users who accidentally click on set tabs aside: when the button is clicked for the first time, you could have a pop-up explaining that the tabs have been set aside and why some people find this useful, and giving the user the option to bring the tabs back and remove the set tabs aside button.
Dan_AI4GK
Jan 27, 2020Iron Contributor
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.
- JaturnJan 28, 2020
Microsoft
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.