-
Notifications
You must be signed in to change notification settings - Fork 36.2k
-
Notifications
You must be signed in to change notification settings - Fork 36.2k
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
Unsynced wallet status should be more apparent #8060
Comments
Agree with @laanwj. I pick this up. |
@laanwj how do you envision this? I'm interested in implementing it, but I don't see a way that's not massively redundant. We already have the sync progress bar and the text warning to the left of it. What do you think about adding a red or yellow caution to the right of the warning text, to draw attention to it? That seems to best fit with what already exists. Augmenting instead of duplicating. I could change the mouse over text from the sync bar/text to reflect the extra warnings you describe, and add this mouse over to the new warning icon as well. How does all that sound? |
@Tyler-Hardin sounds good to me! |
I have a different approach: Users could "click-away" that modal information layer. But at least a click-away action is required. Once the layer has been clicked away, we could go back to the current state where we show the exclamation mark warning icons |
Sound good as well. Make sure to include a "[ ] Never show this again" toggle. |
Most of this was done in #8371. Not sure if those should be addressed: (copied from OP)
|
Hm, doesn't the overlay take care of all of those? I don't mind that they're not specifically implemented as mentioned there, that was just an idea. |
It is missing the fee estimation part, but I think this can be done later. |
Currently the wallet shows warning triangles on the "Overview" page when the client is not synced.
Looking at the volume of mail I receive from people confused by unsynced client behavior, as well as issues like #7235 this is not enough.
I think it would make sense to:
The text was updated successfully, but these errors were encountered: