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.
Jerry Jackson commented
Teams effectively has no caching ANYWHERE. Even chat history is painfully slow to try and browse through (up OR down!) :@
My teams only use a few web-based applications, and being able to add this as an option for a website tab would be a fantastic win!
Yes, I have teams that only require a couple of applications that are web-based. If we could allow background/persistent website tabs so they don't lose their work if they go to "Chat" or another tab.
That would be fantastic!
I have the same issue, this is really annoying and I believe it might be correlated with the new sign in experience.
Stephane Dorail commented
We lost file opened in Teams tab when we switch between Chat tab and Teams tab. This is an awkward in daily use.
Could you identify this point a give me your opinion about this ?
Tom Fichtner commented
Same issue here.
Still not fixed in version 1.0.00.30452 from November 14, 2017
Michael Florentin commented
We have a channel with a tab with a Word document which lost a large comment I was working on because Teams/Word does not recognise and respect standard OS keyboard shortcuts.
Steps to reproduce:
1) Create a channel in Teams with a Word tab containing a Word document.
2) Add a comment to a piece of text in the document and start typing the comment.
3) Press alt+left arrow.
4) Teams will switch to the tab to the left of the Word tab silently loosing the comment with no obvious way to restore it.
This is problematic because a) Word silently looses data and b) Teams/Word does not respect OS keyboard shortcuts that are ingrained in user muscle memory.
Tested on Teams 1.0.00.28451, macOS 10.13
The creation of tabs with the Launch fullscreen setting enabled needs checking for any contribution to this issue. Its not obvious if manually 'expanding' a tab is equivalent to the intent of the setting in tab creation called 'launch fullscreen'.
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.