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.
Bart Hegarty commented
Is there any update on the progress in providing a patch for this opportunity?
JONATHAN SOURKES commented
This requested feature is incredibly valuable. It is near impossible to use Teams for collaborative documents when a chat can pull you away from your work.
Please add a pop up window for chats that doesn't navigate you away from your work.
Matt Hopkins commented
I notice that my asp MVC web app gets a new session every time the user navigates to a different link - that doesn't happen in a normal browser session.
Jof Neuhaus commented
This thread opened early 2017. I'm glad to read Microsoft is working on it. However, can you give us a rough estimate when to expect this feature?
If you can't give us a date, it would be great if you could let us know if this feature will be implemented before a new platform/software is launched to replace Teams.
Sean Ellis commented
They don't need to be kept in memory in their entirety (although that is the quickest way to do it).
But they must retain their state. Switching away from a tab and back again must leave you in the same state as when you left.
For instance, in a conversation, this requires saving your position in the chat and any half-composed messages - a few kilobytes of data at most. The rest can be recreated on demand.
As a cheap speedup, also cache just the messages displayed on screen, display them immediately and then reload the rest of the conversation history in the background.
This then becomes one part of the requirement to be able "tear off" any tab into its own window - another request that's been asked for repeatedly for years.
Important Note: My issue (and I believe many on this thread) is not with the desktop client but the o365 WEB APPLICATION. Nearly every cloud based web application supports multiple tabs. This is a MAJOR defect that MS Teams does not support multiple tabs. This is how the workforce has now worked for 20 years.
yes please remove reload
Taylor M commented
This is FANTASTIC news. If there is a preview for it, I’d like to provide feedback. This is something I’ve wanted to implement for our organization since Teams launched!
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.