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
Channel sorting broken #1088
Comments
Assuming this is due to #1064 |
Interestingly I'm not able to reproduce it. Have you ensured you did an npm run build, @PolarizedIons (not that this should make a difference for this particular issue, one would think) |
Yep I did, @YaManicKill. Recloned to be sure and still an issue. |
Pinging @xPaw about this. |
I don't have this problem. @PolarizedIons are you sure it's not a local change? Also, what browser do you use? |
@bews Chromium Version 58.0.3029.81 (64-bit) on Arch Linux, but the fact that it persisted after a refresh (and diffrent in fact) leads me to believe it isn't a browser issue. No local changes - I did a fresh reclone to test that |
FWIW, I can repro in Safari and Chromium |
Probably #1064 broke it, unsure why though. |
Just adding more info to this: it doesn't seem to happen when you "manually" join networks/channels. I connect though ZNC so it could be caused by that, or the amount of channels/queries it opens |
I can't reproduce this. I also connect to ZNC. |
Fixed in #1115. I think the ZNC thing was just a red herring |
Running on master (dd5e50f).
As you can see the order is messed up when syncing to other clients, but the strange order also persists when refreshing. (Also note how the network lobby isn't where it should be)
https://gfycat.com/TalkativeKindlyAlbino
The text was updated successfully, but these errors were encountered: