Full stack web dev.
Studying FP web development approaches, while helping Mission Bit create paths to programming for underserved public school kids.
Previously @ Gradescope.
As others have said, the "problem" is that the buttons are doing double-duty. Once you're putting two things in one place, I'm not sure there's a "right" way to juggle them.
(It's a bit like mutable data structures -- when space is at a premium, the place gets prioritized over the stuff that's in it. But if you have to, you make do.)
I think this is one place where skeuomorphism make sense. If something behaves like a toggle, making it look like a switch helps get the point across.
Short of that, IMO ideally the status and the actions have separate homes. Short of that, having a hover state seems better than not having one, but it still excludes mobile and screen reader users (I think).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
As others have said, the "problem" is that the buttons are doing double-duty. Once you're putting two things in one place, I'm not sure there's a "right" way to juggle them.
(It's a bit like mutable data structures -- when space is at a premium, the place gets prioritized over the stuff that's in it. But if you have to, you make do.)
I think this is one place where skeuomorphism make sense. If something behaves like a toggle, making it look like a switch helps get the point across.
Short of that, IMO ideally the status and the actions have separate homes. Short of that, having a hover state seems better than not having one, but it still excludes mobile and screen reader users (I think).