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.
Without this feature is almost impossible to work on different wikis at the same time.
Agree. It's completely absurd that I have to wait for a document to load all over again, and find my place all over again, when I simply click to a different chat. We need this change!!
As we are phasing out Skype for Business, multiple active tabs is an absolute must. In addition to needing to view multiple resources in Teams at once, we HAVE to be able to have a chat window open while viewing resources in Teams that are being referenced in the chat.
Yes to this x1000, it is painful to try and work on something, or even just look around for files, and try to chat at the same time, especially if you have active chat's you're trying to keep up with. It would be nice to have an option to either go back to where you were, or have a chat window that could float or minimize on the screen you're currently on.
The Website tab is fairly useless unless you incorporate navigation controls. Once you get deep within a page, you're stuck!
Sean Ellis commented
All views should retain their state when you switch away and back again, and preferably when you log off and back in.
This also ties in nicely with the need to tear off any view into its own window.
Chris Gillotti commented
I completely agree with this need. When you are working in a document and get a new chat notification, the document window closes out and you have to navigate back to it every time you want to read the message. It adds a lot more steps to getting work done.
Charlotte Sanchez commented
Currently if you are co-authoring a document in Teams and have to go away from the Team tab (to click chat to see the latest message), the document closes and you have to click on the teams tab again and reload the document.
It would be nice if Teams pinned an open document to the teams taskbar and keeping the document opening for editing. this way a user can easily go back and forth between chat and the document.
Absolutely agree. The more apps you integrate in Teams, the more annoying the clicking and switching between apps becomes. To make this work properly, you would almost have to use the Internet browser principle of having different tabs for active sessions, i.e. not the existing tabs within a channel but tabs for Planner, Wiki, e.g. two active channels, a chat, etc.
It would be great if with in Teams I could open tabs like in we do in any modern Browser, to keep a chat open, a phile and schedules
I have a problem with Microsoft sites and sites that use SSO. I just want them stay signed in! My browser can remember log me in automatically. I wish the same experience happened in Teams.
We are attempting to fully leverage Teams using mini-apps like Website integration. We use a handful of intranet sites on a regular basis - referencing between them. Having all in one pane-of-glass is great...except that switching means starting over each time. :-/
Can't you freeze the location/context when switching away? Otherwise I'm back to opening browser tabs, and losing support for staying within Teams.
Mike Beall commented
This is especially painful when using website integration... you leave the tab for a moment to use another tab and upon return, you have to start over. This is such a hindrance to effectively working back and forth between tabs. Creating some type of user session on the tabs would be fantastic so that you could literally jump tab to tab and not worry about losing work.
It would also be nice if it remembered my password for the target website.
The browsing capability should also have a function to remember my password for the target website.
Sean Ellis commented
This is a common request. The tabs should at least keep their state when you switch away, and it would also be useful to "tear off" tabs into their own free-floating windows. There's a longer thread discussing this here: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16926739-multi-window-for-chats-and-more
I was working on a excel file tab in the team channel, and suddenly some one messaged me, I checked that file and when I turn back ,I have to reload the tab again.
Can we please have a individual area for chats so that I can same much time reloading the tabs?
Marc Roussel commented
I was about to write a new one but this is exactly the problem I face often with MT. For instance if I go to TEAMS tab and let say I open an Excel file, if someone chat me in CHAT tab when I come back in TEAMS TAB I lost the file that was opened. Very bad design and need a fix ASAP.
Jen Singh commented
The tab state should include a memory of whether the Wiki & OneNote TOCs (tables of contents) were expanded or collapsed last time I was there. And which page I was on, and where I was on that page.