Keep Tab in Memory when Switching to Chat / Other Tab - Prevent Loss of Edits, Files, Login credentials
Switching from a Tab to Chat / Teams / Other Tabs causes the Tab to close, causing you to have to reopen the Tab (actually having to navigate to it again inside the team). This will reload the tap and all content before the Switching will be lost.
1. Tabs open in Team gets reset - when switching between Teams in Team View
2. Tabs reload - when switching between Chat and Team View
3. Content (edits, files etc) on Tab gets lost (Happens both for to Issue 1 and 2)
4. It makes you re-sign-in to Planner, Jira or whatever third-party tab you were using
1. Tabs should stay open in the related Team - having to navigate and reopen a tab every time is very bad for workflow (Relates to Issue 1)
2. Tabs should be kept in memory - Reloading the tab every time is Very slow (Relates to Issue 1 and 2)
For us the main issue is that we lose edits, files, data etc when we navigate away from a tab to a chats or a different tab as the original tab reloads. We really can not be loosing data.
I see many of other issues on here that are related? I will list them here and ask that they get merged.
I will also comment on all the other issues and ask that people come here to vote and list more issues so that I can keep this issue updated with requests.
The team is working on changes to the desktop client so recently opened tabs are kept in memory, as long as it doesn’t use too much memory.
I will keep you posted as we make further progress.
Not just desktop but web app also. Tx
Christian Herø commented
Good to see status "Working on it" I would ease onboarding to Teams and truly make Teams the hub it aspires to be.
Peter-Ross Cuthbert commented
Absolutely need this feature. I think the best way to handle it would be to offer the user an option to "pin" or "keep loaded in background" in the tab settings. This way it's up to the user to manage memory. I can't see it being anymore demanding than having a ton of browser tabs open though and a lot of things I would usually have open in a browser could then be moved into Teams.
I think it would also be beneficial for tabs to be able to display notification badges/tab notifications for things like putting your Outlook into a tab.
Wayne Mceachron commented
I would like this feature. I want to vote comment do whatever to help create momentum. Thanks!
This is very annoying, disgusting and disturbing to work in team as you cannot open chat window and Teams folder window at the same time. And every time it close all file, subfolders when you switch to other tab in Teams. I see in this forum that this issue is reported to Microsoft long back and its surprising to see that they are not doing anything on it. Do anyone has latest update on this issue as what is Microsoft's feedback on this?
[Deleted User] commented
please do this...
It's especially frustrating when you use PowerApps to integrate a feature:
The app reloads everytime you switch tabs, resetting input.
Would make Teams much more user friendly and compatible to our needs
This is one of the biggest complaints we get from users.
We are trying to get Teams adopted here and Tabs not retaining their state is going to make adoption alot harder. The scenario we have is there is a team that need to check between two web based systems. Currently when switching between tabs they will be logged out of each system and lose any unsaved data.
It is really painful - application must to keep state. You need to make it configurable - that application will decide if TAB should be refreshed or not
I do agree, Teams should support this kind of multi-tasking
My group edits a lot of files within Teams. So frequently I will instinctively click on a new chat that someone sends me and lose my place on file, having to renavigate to it and click "edit" again. If I'm careful, I'll open a browser version of Teams to chat in, and continue editing my file in the Teams app, but this shouldn't be a requirement.
@all - I have written to support and they said they will send it to the correct department but I never heard back again...
More issues to merge:
@Kyle S - thanks for listing more here to merge - I will contact support to request a merge
Kyle S commented