Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Improve usability of Connection Dialogue #7112

Closed
bnvk opened this issue Nov 21, 2017 · 2 comments
Closed

Improve usability of Connection Dialogue #7112

bnvk opened this issue Nov 21, 2017 · 2 comments
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. P7-nicetohave 🐕 Issue is worth doing eventually.

Comments

@bnvk
Copy link
Contributor

bnvk commented Nov 21, 2017

Currently, the Connection Dialogue is a bit technical and not as user friendly as it could be. For instance when no websockets token exists, the message reads:

Unable to make a connection to the Parity Secure API...

A more user friendly message would be something like:

Unable to connect to the Parity app...

There are multiple Connection Dialogues throughout the application, so I will send more detailed specific suggestions / fixes in individual pull-requests.

@5chdn 5chdn added F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M7-ui P7-nicetohave 🐕 Issue is worth doing eventually. labels Nov 22, 2017
@5chdn 5chdn added this to the 1.9 milestone Nov 22, 2017
@5chdn
Copy link
Contributor

5chdn commented Nov 22, 2017

Thanks, pull requests are much appreciated :)

@5chdn 5chdn modified the milestones: 1.9, 1.10 Jan 5, 2018
@5chdn 5chdn modified the milestones: 1.10, 1.11 Jan 23, 2018
@5chdn 5chdn modified the milestones: 1.11, 1.12 Mar 1, 2018
@Tbaut
Copy link
Contributor

Tbaut commented Apr 24, 2018

Moving to a new repo, we will not migrate low prio issues. Please reopen it in the new repo if you believe it should be addressed: https://github.com/parity-js/shell/issues/new

@Tbaut Tbaut closed this as completed Apr 24, 2018
@5chdn 5chdn modified the milestones: 1.12, 1.11 Apr 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. P7-nicetohave 🐕 Issue is worth doing eventually.
Projects
None yet
Development

No branches or pull requests

3 participants