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.
This issue is not constrained to Planner tab. It happens for Smartsheet integration also likely meaning that the principle design for Teams tab reauth is broken for Chrome users.
Some more detail on this below and I hope dev could revisit what a silent implementation means.
It is not silent in so much as it opens a new tab in the browser window, specifically, the one with the most recent focus (ie. clicked in).
Consider that Edge doesn't support profiles so you won't see errors with users who only have one account and Edge.
The confusion to users is obvious when using Chrome Profiles, because Teams can inadvertently launch the tab into an inappropriate Chrome profile window i.e. because the user had focus there and used for a different account.
Please consider that each profile probably has a different login context and signing into another account will log out the other for all of the tabs in the browser profile. Hence the confusion.
Perhaps implement an embedded simple web client to Teams that could be used for for authenticating silently (or even a new feature for previewing a link on-hover).
When I open a tab (a OneNote tab for instance) there is a 2 - 3 seconds delay while it loads.
This even happens everytime I switch tabs, which is extremely annoyng. Maybe you could implement a cache or something to prevent this?
Christophe Pratlong commented
That issue is preventing my team and myself to use MS Teams on a daily basis :(
Emmanuel LANDAIS commented
Yes this is the same with other external web.application
Password is memorized on navigator, but not on teams... For digital changes management it's difficult ...
Please, do it quickly ! :)
clicking on planner tab forces you to authenticate again even though logged into teams on PC. I found an old topic that says this was fixed but, I am having the issue today, and two days ago I received an update with a message that I had the latest version of teams.
I wholeheartedly support this request!
I conducted a pilot with MS Teams with my classes last year. The complaint that students had (and of course I experienced it as well), is that it takes "forever" to load PDF's in one tab, go to another tab to check something and go back to the first (pdf) tab, only to once again wait for it to load....
So, we definitely need better performance in order to improve user experience! I will go so far as to sat that this will determine whether or not Teams will convince teachers to completely switch...
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.