-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
develop.element.io
with Spaces enabled switching rooms and spaces on its own
#17017
Comments
I'd like to apologize to anyone who has been affected by this. It looks like something I have encountered before but wasn't able to repro then. @tanriol, could you please try out the live preview here when it's available and confirm that it solves the problem? I am still having issue trying to find an exact repro case |
To reproduce:
|
I haven't managed to reproduce the problem in the live preview. However, note that the "Manage and Explore" context menu entry on another space is useless with this feature because it causes a space switch and then a room switch to the remembered one. |
Yeah, this is a bug |
Also I'm not sure how to get out to normal state now - "Clear cache and reload" does not seem to kill this remembered room and your fix is in the save path, not load, so it probably won't do that. Looks like I'll need to clear site data completely. |
If anyone has any further problems with this, please visit this room |
Description
After a recent
develop.elements.io
update mydevelop.element.io
client with Spaces enabled got stuck in an infinite loop switching between rooms and spaces on its own without any additional user input. I've got a number of private spaces for grouping rooms and the loop involves at least one room included in more than one space and both spaces that include it.The weird switching started before the loop and looked like this:
Environment
develop.element.io
with Spaces enabled, Firefox Nightly, LinuxThe problem started after an update that included matrix-org/matrix-react-sdk#5795, which looks like a likely cause, so cc @SimonBrandner @t3chguy
The text was updated successfully, but these errors were encountered: