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

Not a Bug, but an irritant #1993

Closed
cyberduck opened this issue May 1, 2008 · 1 comment
Closed

Not a Bug, but an irritant #1993

cyberduck opened this issue May 1, 2008 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented May 1, 2008

dedebed created the issue

OK, so this isn't a bug, but it is an irritant.

I recently updated Cyberduck, and when it restarted after the installation, I got a message that said this (see attachment):

"Cyberduck has been updated. Do you want to allow the new version to access the same keychain items (such as passwords) as the previous version?"

Then my choices were a "Don't Change" button, and a "Change All" button.

My beef is that the question in the Cyberduck update message is a Yes or No question, but my choices have nothing to do with "Yes" or "No". Likewise, the message does not mention the word "change" at all, so that just adds to the confusion.

My recommendation would be that if you ask a Yes or No question, provide buttons that say "Yes" and "No". You can't get much more clear than that.

Thanks for listening.

Mark Neukom


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 1, 2008

@dkocher commented

Thanks for your detailed report. The dialog is provided by Apple and I cannot change it. However, Cyberduck is now code signed which should make this dialog disappear after you have trusted it once.

Loading

@cyberduck cyberduck closed this May 1, 2008
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants