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

Scroll to bottom button doesn't disappear #1206

Closed
1 task done
zanedb opened this issue May 27, 2017 · 6 comments
Closed
1 task done

Scroll to bottom button doesn't disappear #1206

zanedb opened this issue May 27, 2017 · 6 comments

Comments

@zanedb
Copy link

zanedb commented May 27, 2017

  • I have searched open and closed issues for duplicates

Bug description

The scroll-to-bottom button (down arrow in chat) does not disappear and stays blue when scrolling all the way down.

Steps to reproduce

  • Receive some texts
  • Wait for the down arrow to appear
  • Scroll down all the way using the scrollbar or mouse wheel
  • The button should stay there

Actual result: The button stays there.
Expected result: The button should disappear when scrolling to the bottom.

Screenshots

capture
This is the original screenshot.
capture2
In this screenshot, 2 is the button & 1 shows that I have scrolled down all the way.

Platform info

Operating System: Windows 10
Browser: Google Chrome

Signal version: 0.40.0

Link to debug log

Here is the debug log.
xxx and yyy and zzz are all different phone numbers, redacted for privacy purposes.

@deutrino
Copy link

I can confirm in Signal 0.40.0 on Chromium 58.0.3029.110 (Linux).

@scottnonnenberg
Copy link
Contributor

Hey there - sorry about the inconvenience! I expect that this is due to the same root cause as #1205, and is similarly fixed by #1202.

If you get a chance, we'd love some help verifying that this behavior is fixed. It's pretty simple to check out the repo and then load the unpacked extension into Chrome: https://github.com/WhisperSystems/Signal-Desktop/blob/master/CONTRIBUTING.md#installation. If not, we'll have an official update with the fix out soon.

@deutrino
Copy link

I tested on a non-HiDPI Linux box and this bug appears resolved by the build.

@cybre-finn
Copy link
Contributor

cybre-finn commented May 31, 2017

I can confirm that, not reproducible on the newest build, anymore.

@zanedb
Copy link
Author

zanedb commented Jun 1, 2017

Well, I'll go ahead and close the issue then. @scottnonnenberg, when will this be released?

@zanedb zanedb closed this as completed Jun 1, 2017
@scottnonnenberg
Copy link
Contributor

Tomorrow evening is the current plan!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants