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
I get really frustrated by the "mark all as read" confirmation - it turns a common task from one click into two.
Let's remove the confirmation, but show an alert when clicked ("All discussions were marked as read") with an undo button which will revert the change. We should also show a tooltip on hover of the button, to make it more obvious what the button does.
The text was updated successfully, but these errors were encountered:
Before we update the readTime, we can cache its previous value in a variable. Then if the undo button is clicked, we simply make a request to update it with the old value.
Could we keep this entirely to the frontend? Maybe store requests like this in a queue in the frontend app, add an alert with the option to undo. If undone, it's removed from the queue. If not, after 10 seconds or when the page unloads all such requests are sent. If the user tries to navigate away while the request is being sent, show the "are you sure you want to leave" popup, which should provide ample time for the request(s) to complete.
I get really frustrated by the "mark all as read" confirmation - it turns a common task from one click into two.
Let's remove the confirmation, but show an alert when clicked ("All discussions were marked as read") with an undo button which will revert the change. We should also show a tooltip on hover of the button, to make it more obvious what the button does.
The text was updated successfully, but these errors were encountered: