Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
fix(MessagesList): fix resizeObserver and scrolledToBottom state update #14327
base: main
Are you sure you want to change the base?
fix(MessagesList): fix resizeObserver and scrolledToBottom state update #14327
Changes from all commits
07d921e
80c7649
3f6b9d8
6a6a668
413abe7
0d2ea65
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After swtiching to conversation, handleScroll is triggered. Regardless of container height, it sets value to false (whereas it shouldn't for non-scrollable chats)
For scrollable chats it also shouldn't set to false, when receiiving message (handleScroll is triggered with 'down' direction)
For just opened chats, however, it should still set to 'false', if chat is not at the bottom (we know that from previous 'if' block'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// If successful, deletes the temporary message from the store context.dispatch('removeTemporaryMessageFromStore', { token, id: temporaryMessage.id })
temp message is removed before processing the message in
postNewMessage
Also,
processMessage
in multiple points, I wouldn't risk updating the last read message there. As suggested before, it should rather focus on post new message only. What's odd is that the current addition already exists there but it wasn't working efficientlyhttps://github.com/nextcloud/spreed/blob/main/src/store/messagesStore.js#L1276-L1291
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it exists and works for text messages only. File share (with /without caption) is a one-way, a we will receive a feedback only from message polling
postNewMessage can do it, as we receive a message object as a response and can replace it safely