-
Notifications
You must be signed in to change notification settings - Fork 98
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
more graceful failures #1511
Labels
Comments
let's do it! thx for opening this issue |
faboweb
added
the
split 🍌
issues that need to be split into several smaller issues with reduced scope
label
Nov 6, 2018
@jbibla in which cases would |
good question. i don't think we will end up in this situation - we can probably not use this at all. |
faboweb
added
epic
and removed
split 🍌
issues that need to be split into several smaller issues with reduced scope
labels
Nov 7, 2018
Working on this in #1533 |
Done in #1533 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
this may be covered by some other tickets and should be addressed in the sprint after gov1 ... but i wanted to log it as an example of an opportunity for improvement.
if you refresh voyager but voyager cannot find a good node to connect to this is what the user sees:
2a. a more graceful failure = do not dispay this full screen modal - but instead rely on the network-connectivity-bar to change states from green to orange and display 1 non-invasive popup that says "we're going to keep trying to connect to a good node for you. in the mean time, your experience may be degraded and we would recommend against making any transactions".
2b. part two of this should include disabling all submit buttons and some in app messaging about how maybe some of the data is not accurate.
The text was updated successfully, but these errors were encountered: