-
Notifications
You must be signed in to change notification settings - Fork 3
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
Extra space appears when the most recent message of the chat is selected and then unselected #371
Comments
I searched the codebase for "scrollThreshold" but didn't find anything. Am I missing something, or can you link to the relevant code maybe? |
Apologies for not mentioning the full term earlier—it's related to the values |
Interesting, I'm not able to reproduce the issue following the steps: Kazam_screencast_00000.mp4Can you please note your OS in the description so it will be easier to investigate when we get to it? I'd also like to request that we rename the ticket to describe the problem you're seeing. Then note potential causes in the description, rather than starting with a proposed solution. I don't think the right solution will be to set the SCROLL_BOTTOM_THRESHOLD to 0, since it is a constant for configuring the infinite scrolling. Infinite scrolling is fiddly to get right, so I wouldn't be surprised if there are other bugs hiding in there as well. In general I'd be in favor of swapping out our code for a 3rd party library it if we find a good one. |
Updated the operating system. |
When we select a message containing media (If the message was last message in the chat) and unselect it, it introduces extra space between the input box and message.
My understanding
The scroll threshold value should reset to null when the most recent message in a chat is unselected. However, this reset is not happening, which results in extra space between the input area and the most recent message, leading to unexpected scroll behavior.
Steps to Reproduce:
Operating System
The text was updated successfully, but these errors were encountered: