You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When the mark all as read and delete feed functionality are used on a feed with more than several dozen unread posts there is a wait while the action is executed but the app does not communicate this in any way. If the user attempts to use the app whilst it's trying to delete a feed or mark items in a feed as read the app won't work.
This is okay when the wait is a few seconds, but when it's a few minutes then that becomes a problem.
Describe the solution you'd like
When an action that commonly takes a long time is called a progressbar should be there to inform the user that something is happening and that progress is being made towards the actions completion. Preferably the progressbar would also show the number of feed items that still need to be marked as read/deleted.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When the mark all as read and delete feed functionality are used on a feed with more than several dozen unread posts there is a wait while the action is executed but the app does not communicate this in any way. If the user attempts to use the app whilst it's trying to delete a feed or mark items in a feed as read the app won't work.
This is okay when the wait is a few seconds, but when it's a few minutes then that becomes a problem.
Describe the solution you'd like
When an action that commonly takes a long time is called a progressbar should be there to inform the user that something is happening and that progress is being made towards the actions completion. Preferably the progressbar would also show the number of feed items that still need to be marked as read/deleted.
Additional context
N/A
The text was updated successfully, but these errors were encountered: