Skip to content
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

Message ordering can get very broken in the timeline on bad connections #23

Closed
ara4n opened this issue Aug 29, 2015 · 2 comments
Closed

Comments

@ara4n
Copy link
Member

ara4n commented Aug 29, 2015

On a bad connection, messages can end up shown in entirely the wrong order in the timeline. This may just be SYJS-18, or it could be something worse going on.

@ara4n ara4n added the T-Defect label Aug 29, 2015
@ara4n ara4n modified the milestone: Ragnarok Nov 29, 2015
@ara4n ara4n modified the milestones: v0, Ragnarok Dec 13, 2015
@ara4n
Copy link
Member Author

ara4n commented Dec 13, 2015

@kegsay: does v2 fix this?

@ara4n
Copy link
Member Author

ara4n commented Dec 22, 2015

empirically it looks like it does; i couldn't reproduce with a fake-crippled GPRS connection in Chrome

@ara4n ara4n closed this as completed Dec 22, 2015
dtygel pushed a commit to coletivoEITA/riot-web that referenced this issue May 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant