You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Accounts seem to share the same list of active and inactive tabs, and not have their own separate lists
To Reproduce
Steps to reproduce the behavior:
Open up a new tab, with a server that only the first account has access to
Switch to another account, which does NOT have access to the same server
Note that, after switching, the original tab persists, but obviously it doesn't lead to that channel
Switching back to the original account with access to that server will cause the original tab to lead back to the Friends page
Expected behavior
Tabs that are stored on the original account should be removed when switching to an alternate account, and restored when heading back to the original
Discord version: Stable, but from testing this also occurs on both PTB and Canary
Compact Mode: Disabled
Additional context
Also had a look to see if reloading the plugin itself, or Discord entirely, would work - Neither did, unfortunately. Nothing in the logs (except for CT starting up correctly) was also spotted, either
The text was updated successfully, but these errors were encountered:
Describe the bug
Accounts seem to share the same list of active and inactive tabs, and not have their own separate lists
To Reproduce
Steps to reproduce the behavior:
Friends
pageExpected behavior
Tabs that are stored on the original account should be removed when switching to an alternate account, and restored when heading back to the original
Screenshots
https://github.com/aarondoet/BetterDiscordStuff/assets/75092921/fb2e050e-3da7-466b-b712-7812a30a313b
Information:
Additional context
Also had a look to see if reloading the plugin itself, or Discord entirely, would work - Neither did, unfortunately. Nothing in the logs (except for CT starting up correctly) was also spotted, either
The text was updated successfully, but these errors were encountered: