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

Closing update dialog force update instead of postponing it #2831

Closed
MonoS opened this issue Oct 25, 2018 · 1 comment · Fixed by #3896
Closed

Closing update dialog force update instead of postponing it #2831

MonoS opened this issue Oct 25, 2018 · 1 comment · Fixed by #3896
Labels

Comments

@MonoS
Copy link

MonoS commented Oct 25, 2018

Bug description

When the update dialog show up at startup closing it will update the application instead of postponing

Steps to reproduce

  1. use an old version
  2. the update dialog show up
  3. close the dialog

Actual result:
The update is executed

Expected result:
The update should be postponed

Platform info

Signal version: 1.16.3

Operating System:

Windows 10 1803 x64

@MonoS MonoS changed the title Closing update dialog force update instead of postponing update Closing update dialog force update instead of postponing it Oct 25, 2018
@Herohtar
Copy link
Contributor

Herohtar commented Jan 17, 2020

This is still an issue in v1.29.6.

Specifically, the showUpdateDialog function is configuring the message box options to use RESTART_BUTTON as the cancelId.

cancelId: RESTART_BUTTON,

According to the dialog.showMessageBox documentation, cancelId is "The index of the button to be used to cancel the dialog, via the Esc key." This is the equivalent of clicking the close button (X).

Restarting Signal and applying the update is not cancelling, and is not the behavior people expect when clicking close or pressing Esc on the update dialog.

cancelId should be set to LATER_BUTTON instead.

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

Successfully merging a pull request may close this issue.

3 participants