If the user manually scrolls to the bottom of a chat, enable autoscroll for future messages #17546
Conversation
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
|
at one point, a 32px scroll chin made it impossible to scroll to top (to read the first few messages) without having it immediately snap to bottom on certain chats without a sufficient number of messages. does that still happen? if so, should we try 16 maybe? |
|
@schlawg From my testing, I can't seem to reproduce this issue with 32px, both on my computer and phone. Also for this PR, the minimum values I've found that make autoscrolling work:
|
|
What's your browser, zoom level, and OS? |
|
@schlawg On computer Windows 11, 100% zoom, and both chrome and edge. For iphone it's safari, at default zoom. |
|
got it, thanks. i missed the manually scroll part (and was looking at broadcasts) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Essentially just undoes e0f9d8e, going back to the original value of 32 @schlawg used in e0f9d8e's parent commit (c3bdbba).
Screen recording showing current behaviour (the tab where I'm moving the scrollbar is for "John1"):
Screen.Recording.2025-05-18.224601.mp4