That’s a Chromium behavior, and that’s fine, if you want to collapse Discord so it doesn’t occupy much space, then pin it, collapsing Tab Groups is meant to freeze all the tabs unless they are playing audio or something that actively uses the tab, not being in the background throttled like Discord would be.
It has nothing to do with Memory saver or anything, it’s just default collapse group behavior that Chromium added like 3 years ago, when they added the flag to control it and then removed it to make it default.
Opera doesn’t use native Chromium UI, or native Chromium features in their workspaces or groups, Brave does, Brave doesn’t use a custom UI like Opera or Vivaldi, and that’s why using extensions to control groups work in Brave and Edge but not in other Chromium browsers, we have to assume that’s why these behaviors are working ‘as expected’ in Brave and not Opera. So it is like comparing apple to oranges to mention Opera.
If you test it on Edge, it will act the same as Brave, the only difference in Edge is that it is so easy to see the ‘reason’ for tabs not to sleep, you can easily deal with it.
Also, for some reason Edge will not put tabs to sleep, if there are duplicated pages with the reason Tab is sharing its BrowsingInstance with another tab , but once you have unique tabs, it will put them to sleep just the same as Brave ‘freezes’ them.
Also, when you un-collapse groups in Edge, they don’t come out of sleeping, you have to click on them individually for them to ‘wake up’, while on Brave they unfreeze immediately after un-collapsing the group.
One thing both do (easy to see in Edge) is that if a page has Notification permissions, it will not put them to freeze, so how are you getting notifications if you haven’t allowed them in Discord? Those tabs shouldn’t then be put to sleep because of that permission, even if the tabs aren’t doing anything, if they have the permission, they will not be put to sleep, so you either use pinned tabs or give notification permissions to Discord.
Also, permissions for ‘normal’ windows are not the same as Private or Tor windows, so only because you add [*.]discord.com to notifications, it doesn’t mean it will allow notifications when you browse in Private windows, they have to be manually added after opening a window, and then check the option Current Private session only.
So in resume, if you are going to use Tab Groups with one of the worse privacy nightmare websites like Discord is, that’s basically what you have to do and know. Chromium upstream behavior, Edge implemented discard page better, they work the same and the only difference is how Edge has this dumb feature not to sleep tabs only because they are duplicates and how Edge keeps the tabs in the sleep state until you click on them, and the only workaround is to allow permissions or pinned tabs.
One cool thing, Nightly added “Shared Pinned tabs” feature, when you pin a tab, it will be shared across all windows, who knows when it will be available for Stable, but someday it will, and pinned tabs will be more useful than what they do now. Just adding the little Nightly note, so you know pinned tabs can be a nice alternative in the future, or today if you use Nightly and not boring Stable.
