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.
It is really painful - application must to keep state. You need to make it configurable - that application will decide if TAB should be refreshed or not
I do agree, Teams should support this kind of multi-tasking
My group edits a lot of files within Teams. So frequently I will instinctively click on a new chat that someone sends me and lose my place on file, having to renavigate to it and click "edit" again. If I'm careful, I'll open a browser version of Teams to chat in, and continue editing my file in the Teams app, but this shouldn't be a requirement.
@all - I have written to support and they said they will send it to the correct department but I never heard back again...
More issues to merge:
@Kyle S - thanks for listing more here to merge - I will contact support to request a merge
When switching between Tabs with i.e. a website linked within, the website is fully reloaded when switching back to the site. This is very annyoing if the reload causes i.e. a ticketsystem to reload a already half done ticket if there was just the need to check some info from another Tab.
I don't see a good reason why a Tab needs automatic reload. Maybe a simple Option if the page should be reloaded by hand or automatic will give TEAMS a push in performance, too.
You do a realy good job with teams - thank you all!
Wendy Gramer commented
This is especially annoying when we are using Planner for a stand-up or other meeting. If we need to switch windows to get a file or look at a chat, the Planner filters reset.
Amna Jalal commented
Yes this get very troublesome. I am on chat with a team member and I want to have a look at the task assigned to me at the same time. I filter the tasks and go back to the chat tab. Then when I switch back to the Tasks tab, the filter is lost! This needs some serious attention please. Thanks
Bump for this, its crazy annoying, and also, i think you can merge these in:
Clearly, the dev didn't put "efficiency" into consideration here. This is just dumb. We're not in the early 2000s where people would peek the **** out of your shoulders to see what's up. duh
J Tenneson commented
Agree - we have a standard process I need to follow which requires creating copies of a template file (often several at a time) then going back and editing them (I know it isn't a great process, but it's what we have).
When I enter a document to make edits, then hit edit, as a user I expect that:
WHEN I open a file for editing in Teams and THEN hit the back arrow
I RETURN to the sub-folder I opened the file in.
Returning to the root directory is not a valuable use case.
I've seen other requests to return to the root directory - but that seems like it could be more easily solved by putting the menu tabs at the top of the file.
Currently the entire window is used by the file you opened. Instead, putting the navigation tabs at the top (Conversations/files/etc) in a collapseable tab (like a ribbon) would seem to provide the ability to return to the root directory while the back button logically would remain as taking you a single step back in your navigation process, to the sub-directory where you were working.
The "Are you still there?" + "I'm back" makes Teams unusable for me.
My workflow requires I work on multiple docs/channels and seamlessly switch between them. To be quite frank, adding this speed bump along with the O365 web applications generally not being as functional as the G Suite versions makes recommending O365/Teams a hard sell to clients not married to Office docs. My clients would go nuts with all the "Are you still there?" messages.
I would have thought the developers of Teams/O365 would encounter this issue and be frustrated enough to fix it.
I find this and the associated "Are you still there" refresh prompt, such a PITA that I'm surprised how few votes there are.
I often work with multiple tabs open such as one for Chats, another for a channel to copy content excerpts from and a third to copy those contents to and the prompts, delays refreshing and sometimes the lost input such as a half completed chat are VERY annoying to me.
Brian Liu commented
We have Deltek timesheet web application that we want to show as a Tab on the General channel. Need the website cached/not refreshed so that users don't need to log in every time they switch tabs.