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.
Any feedback from MS?
This should not be a big deal.
This is really important, when working with multiple Teams.
I use JIRA and Confluence on two tabs on a channel. On restart I have to log in again to all these services, and Teams has no way of remembering my passwords, so I need to remember/type them every time. Very inconvenient compared to just using a browser which can remember your passwords.
Vincent Hocquemiller commented
Good point, and how about also keeping the same context (tab) when switching from a channel to a channel from the same team?
Use case: You are going through a team to check its content, or you are looking for a particular file in a team. You navigate through the channels, but you have to click on the Files tab every time.
Andreas Brandscher commented
Right now, switching between tabs is painfully slow since tab content is reloaded everytime you visit a tab. (Especially true for integrated web services like Wrike)
Joseph Kim commented
Please fix this!
Joseph Kim commented
Please fix this, can't believe this feature wasn't implemented from the start.
Create a new Website tab that points to the excel online editable version.
YES! This is a huge frustration for me when navigating between different channels.
Plenty of user feedback being received that it is poor practice having to do extra clicks every time they navigate between channels. How about adding a minor feature that remembers the last tab a user viewed in a channel, and navigating there when they next use that channel? That would be a huge win in terms of daily unnecessary clicks, Microsoft Server burden and page load waits! Make it a feature that the Admin can enable or disable maybe?
I have made a Website tab for WeTransfer so we can upload files using their service within Teams. However, the way tabs currently work is they have the same effect as closing a window when switching to another tab. Your last position is not remembered and the tab does not run in the background. So in order to upload a file to WeTransfer using the Website tab for example, you need to leave the tab open while the upload is in progress. This removes the possibility of multitasking within Teams.
Perhaps apply some sort of option when setting up a Website tab that says 'run this tab in the background'?
Derrick Krakau commented
I agree, the website tab needs to stay where it was last at, with a home button and back forward buttons. It should really be what effectively amounts to a permanent Edge tab.
Jonathan Vasek commented
It would be nice to return to the same Tab in the previous Channel(s) when switching back and forth.
Preload the content of tabs so that they work in a similar way as regular browser tabs. In this way users would be able to switch from one tab to the other and continue the navigation where they left it without further delays due to tab load time.
Ori Menashe commented
#1 UX problem
Chris Johnston commented
I recently created a tab out of an excel spreadsheet. I can move my cursor around the different cells, but in order to actually edit the spreadsheet I have to open Excel Online, a whole new tab. It would be nice if Excel Online was embedded and used as the viewer, and I could edit right in teams without needing to open a new tab.
Ian Bennett commented
Cache need only be persistent while Team session is open.
Ian Bennett commented
Website (and perhaps other) tabs should act more like browser tabs and not be refreshed every time you navigate away from them and back again.
Marco Lafond commented
the application should remember in which context (tab) I was when navigating between channels.
At the moment, when accessing a channel it always open the conversation tab.
If last time I was looking at the Files tab in channel A, I should be brought back to it when coming back to channel A. (applicable to any tab of a channel)
You are in Channel "A" working on tasks in Planner's Tab and then you see a new post in Channel B, you go see what's new in channel B but when you come back to what you were doing in Planner in Channel A, you are going to Conversations and have to click again on the Planner tab to continue the thing you were doing.