-29 upvotes, 2 direct replies (showing 2)
View submission: Another Mod Queue 2024 update
It's funny, this came up in discussion earlier this week internally :). We are still down to change how we handle this state as well as other parts of the design.
As for the thought process:
- We currently don't have a way to "undo/revert" an approve or remove, but we still want to make sure it's easy to change the state (in case of a mis-click or later discovered additional context). For that reason, we have left the opposing button available by default (as opposed to hiding it behind a menu). This may not be as important as we think. If you think this could be hidden behind a menu, let us know
- Another alternative we've considered is to leave the other button there, but disable it based on the state. Curious if you think this would suffice!
We did actually change the button treatment for things that have been actioned on. It's be "bordered" rather than filled. That said, it may not be enough. Position is an important factor as well.
Comment by stacecom at 13/09/2023 at 23:51 UTC
9 upvotes, 1 direct replies
Changing the button into an undo button would feel like a better fit to me. Treat clicks as a toggle, basically. That's how my mind works, but maybe I'm odd. But keeping it there and making it inactive is a better choice than what's in the video, IMHO.
Thanks for the reply.
Comment by lampishthing at 14/09/2023 at 12:02 UTC
2 upvotes, 1 direct replies
Disabling based on state has a downside too. On mobile I sometimes remove something twice to send 2 removal messages to a user. E.g. on r/relationships there's a requirement to include subjects ages (e.g. 28M) and a TL;DR and there is no better method to chain removal messages.