-
Notifications
You must be signed in to change notification settings - Fork 970
put some "shine" on the ledger notifications #4019
Comments
example 1: Agreed. Status report should switch to something like: Status update not available. Please check your internet connection and try again. example 2: seems like P2 polish to me. ex 3: why not? If it's tomorrow, then hurry up! ex 4: different problem - the contribution date can never be in the past. In this case, always make it the same day? |
also note that in example 2, there is no "Later" button. there should be. otherwise, the only way to get the notification to go away is to click "Review your chosen sites". |
One point I forgot to make here. Most likely, the top bar notifications will not be seen together with ledger screen until user clicks on the CTA button. #2 needs an "Ok" button. I think 24h later is already later. No? |
i suspect that if the active tab is @diracdeltas & @ayumi - your thoughts? |
@bsclifton - can we close this issue now? |
groovy! |
While I haven't tweaked something on the notification bar? |
@luixxiul - i think that as a part of some general refactoring, the notification bar issue above was polished... so, we're done with this issue! |
sweet! |
example 1: if the client can't retrieve the data, how does it know that the account is under balance. seems to me that the "Your account..." status shouldn't be there:
example 2: at the top we're told we have less than 24h to review (great!), but the status gives a date for the next contribution (confusing). i suggest that when <=24h, that the status indicate how long until the contribution. (hint: use the magnificent moment package, e.g.
moment.fromNow(true)
):example 3: when funds are pending, i don't think it makes sense to talk about a 'Next contribution':
example 4: if the contribution date is in the past (this screenshot was taken on 9/15), and the balance is sufficient, then instead of "Next contribution" we ought to have something like "Contribution being processed":
The text was updated successfully, but these errors were encountered: