Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Post & Page Lists: It can be unclear which "undo" view is for which trashed post. #4185

Closed
aerych opened this issue Aug 21, 2015 · 5 comments

Comments

@aerych
Copy link
Member

aerych commented Aug 21, 2015

We support undoing multiple trashed posts, however the undo view does not provide any context about a post that was trashed. We should at least show the title of the trashed post, but maybe some more details wouldn't hurt.

cc @mnt and @adambbecker, We could use some designer input here.

img_0127

@aerych
Copy link
Member Author

aerych commented Aug 21, 2015

Props @koke, who reported the issue

@mattmiklic
Copy link
Member

I wonder if, instead of the undo action being presented on a card in the list, these should be more like notices; temporary messages that go away. Moving something to the trash isn't a destructive action, so it's not important that the user is able to undo multiple move-to-trash actions from the post list. Just 2¢; @adambbecker may have alternative ideas.

@bummytime
Copy link
Member

Just the friendly neighborhood groundskeeper passing through. Looks like this is still an issue:

napkin 33 12-14-16 10 35 05 am

@mattmiklic, I agree this is not a destructive issue and perhaps not really a priority. Any thoughts at looking at a temporary message option, closing this issue, or leaving it be for now?

@mattmiklic
Copy link
Member

There might be some value in looking at a solution more similar to Calypso, where the post doesn't completely disappear, but fades out with the "moved to trash" message overlaid on top. Don't think it's a pressing issue though, at least given other priorities.

@kean
Copy link
Contributor

kean commented Oct 31, 2023

Fixed in #21724

@kean kean closed this as completed Oct 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants