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

UX for update failures over HTTPS #7619

Open
joepie91 opened this issue Apr 2, 2015 · 0 comments
Open

UX for update failures over HTTPS #7619

joepie91 opened this issue Apr 2, 2015 · 0 comments
Labels
Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.

Comments

@joepie91
Copy link

joepie91 commented Apr 2, 2015

As requested, a separate issue. In #6441, the following screenshot was posted of the UX for a failed update attempt over HTTPS:

... however, all the buttons are red and barely distinguishable - this is likely to lead to the user making a wrong (unsafe) choice. A UX change is critically needed here.

Suggested solution:

  1. Update Automatically using HTTPS and Continue to Piwik should be either green, or a neutral color (such as light grey).
  2. Update Automatically using non-secure HTTP should remain red, as it is now.
  3. Update Automatically using non-secure HTTP should be moved to the end of the button list, as the last option.

The above makes the unsafe options unattractive to users, and will make them think twice before using them. More on this can be found in this presentation from the Google Chrome security team.

@mattab mattab added the Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. label Apr 8, 2015
@mattab mattab added this to the Mid term milestone Apr 8, 2015
@mattab mattab modified the milestones: Long term, Mid term Dec 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Development

No branches or pull requests

2 participants