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

[stable21.1] Prevent loading old messages twice on scroll #5209

Merged
merged 1 commit into from
Feb 19, 2021

Conversation

backportbot-nextcloud[bot]
Copy link

backport of #5198

Whenever the old messages are already loading initially when opening a
conversation, a scroll event might call getOldMessages again which would
cancel the previous one.

The initial old messages load is using includeLastKnown=1 while the others use
0. So if it gets cancelled, we will miss the "last known" message as it
won't be included in subsequent calls.

This fix prevents repeated calls to getOldMessages to avoid the above
issue.

Signed-off-by: Vincent Petry <vincent@nextcloud.com>
@nickvergessen nickvergessen merged commit daa3e5a into stable21.1 Feb 19, 2021
@nickvergessen nickvergessen deleted the backport/5198/stable21.1 branch February 19, 2021 11:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants