UX issues in trash, when many entity types are trashable

That's an interesting problem, I'll need to think a bit about what we can do to alleviate it.

Not sure I agree with displaying all trashed entities on a single page, in ✨ Add bulk restore function Active I'm trying to change those listings to use views where possible, and views can't work with multiple entity types :/

In the meantime, I mentioned this issue in #3500162-6: Define how to handle secondary local tasks in entity pages when Navigation Top Bar is enabled → , to make folks aware of the possibility of having so many 2nd level tasks when designing the new Navigation Top Bar.

Thanks for reviewing this issue.

On the side note: Views for those lists would be great, as this would enable more options to configure how those lists look. But I get why it makes my suggestion not very useful :)

So, maybe another option: Maybe it could be achieved with the menu? Like taxonomy is, for example?
So there would be one position "Trash" under content and children menu items with all entity types enabled?

I've been thinking about this problem lately and I think we should add a Compact overview setting that displays the list of trash-enabled entity types in a select element and hides the second-level local tasks.

Let me know if you can test this a bit and what do you think about it :)

Merged into 3.x.

Automatically closed - issue fixed for 2 weeks with no activity.