Keep Tab in Memory when Switching to Chat / Other Tab - Prevent Loss of Edits, Files, Login credentials
Issue Summary:
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.
Issues:
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
Enhancements requested:
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.
David Van De Meer
shared this idea
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.
209 comments
-
Anonymous
commented
Hi, any updates to this ?
-
AM0002
commented
Had to use Teams online to get around this, even a confirmation message on exit would be welcome.
-
Anonymous
commented
A year has passed ... any updates on this? @Alex
-
David Knox
commented
This is quite a crucial factor in making MS extensible - providing third party apps within MS Teams. The User Experience of several apps is just this and is awful and as a result products won't be used if they have to login every time they navigate away from the app / tab.
There is the popout window feature though I may need to into whether the app can be popped out from the offset as popping a app out midway through still requires 'performing another login' which isn't great!
It would nice to have some further information about this - the last update was a year ago!
It always seems that a very broad scripted "we will keep you posted as we make further progress" message is given and then sometimes no further update is given. Surely meetings are raised where an issue is discussed and either put on the roadmap or dis-regarded as not significant.
What we really want to know is whether this is in the pipeline or whether this has been dis-regarded or whether this is a good article on persisting authentication when switching between tabs / apps out there somewhere ?
Thanks.
-
Martin Nguyen
commented
Any updates or workaround for this issue?
-
Anonymous
commented
This is actually one of the shortcomings of "Teams" which keeps me from using it even more often. Many times, I have 2 - 5 chats going on at the same time, I'm checking on files on Teams, and completing tasks. The only workaround so far is to use browser-based and client-based Teams to keep workstreams separate, but ultimately, we lose oversight of what post was viewed where, and which file is currently being worked on (in Browser-Teams, Client-Teams, or in the Desktop-App (Excel, PPT) etc.
I'm male, so multitasking doesn't come easy anyway, and keeping the various parallel workstreams open at the same time is essential to me ;-)
-
Parth Agrawal
commented
@alex,
Can you please provide any update on this issue. -
Anonymous
commented
Dear Microsoft Teams Engineers,
Could we get an update on this please. I'm trying to roll Teams out and include more functionality to enable a 1-Stop-Shop for our staff. The main issues are the losing of positions in Tabs or when linking to a website, you keep having to login each time you go back to the Tab.
It seems that we are not alone in this so any update would be useful.
Many thanks.
-
Anonymous
commented
Please provide an update to the status of development.
-
Anonymous
commented
This would be a well worth while feature
-
Adam Halfhill
commented
Can you fix this by Tuesday? Would be amazing, but I would think this is on a back burner due to the amount of time that has passed. Seems this has been brought into light in a few different post as well.
The desktop version should have been a given. Let "me" determine which tabs to cache, let "me" worry about the performance within the channel. The tabs just feel broken and unproductive like this. Less Teams commercial $$$, more development $$$... pass that on.
-
Luke Johnson
commented
Where's this up to MS ?
-
Timothy Merridew
commented
Not sure if this is also part of the same issue, but with the desktop client it needs to be able to keep track of where you are on websites that have been added as tabs in channels, as we're trying to move to a point where I can put some of our webapps into Teams as tabs rather than just using the web browser but it doesn't work well if you need to go to another tab, channel, or team as clicking on the tabbed website takes you back to the starting url which will usually be the login or home of the webapp.
Could you not work with the edge team on using some of the chromium work they have been doing?
-
Knight Solutions
commented
Much needed
-
Ron
commented
Is there any ETA on this feature? It's really ridiculous that this hasn't been fixed already. So bloody annoying!
-
Eduardo Miller
commented
Hi, could you please give us an update on this? Thanks!
-
[Deleted User]
commented
+1, this is an extremely annoying feature, which makes working experience with MS Teams really bad
-
sc
commented
Can we get an update on this? This issue is making Teams *far* less helpful for teaching.....
-
A L
commented
Hi, could you please give us an update on this? Really important to be able to do this! Thanks!
-
Patrick
commented
Any updates on this? It's been over seven months since it was marked as being "worked on".
It's disappointing that a feature like this doesn't exist, especially given the demand.