-
Notifications
You must be signed in to change notification settings - Fork 313
Fix scroll jump when returning to a channel after WS reconnect #6234
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
Open
VelikovPetar
wants to merge
5
commits into
v7
Choose a base branch
from
bug/AND-1113_fix_channel_jumps_after_coming_back_from_background
base: v7
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+203
−4
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
c18bbd2
Fix scroll jump when returning to a channel after WS reconnect
VelikovPetar 640982d
Merge branch 'v7' into bug/AND-1113_fix_channel_jumps_after_coming_ba…
VelikovPetar 5f3cd6f
Merge branch 'v7' into bug/AND-1113_fix_channel_jumps_after_coming_ba…
VelikovPetar 8b139a2
Merge branch 'v7' into bug/AND-1113_fix_channel_jumps_after_coming_ba…
VelikovPetar d24df19
Merge remote-tracking branch 'origin/bug/AND-1113_fix_channel_jumps_a…
VelikovPetar File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
Just for me to understand: this check for a gap between current and incoming, in that order, right?. What if there's a gap the other way around, i.e. all incoming are older than all current, is that a valid case?
Uh oh!
There was an error while loading. Please reload this page.
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.
Yes this is intentional: This method should never be called with messages other than the latest (known) messages. It is called in the following scenarios:
QueryChannels) - latest messagesQueryChannels)notification.message_new) - again, we should have the latest messages in the response.The other scenario should not be possible (when this method is invoked)