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

"Trash Bin": A way to identify 'trashed' items in the "Recently Played" #3263

Closed
ussher opened this issue Jan 3, 2025 · 1 comment
Closed

Comments

@ussher
Copy link

ussher commented Jan 3, 2025

📝 Provide a description of the new feature

The "trash" feature works great. When I click it it immediately stops playing.

Feature Request: That when I look in my "Recently Played" section of the 'Queue' that there is a way to identify which songs have been trashed.

WHY: Because I'm currently 'liking' all songs that are completely instrumental and trashing ones that I don't like or contain lyrics. Currently songs that have been 'trashed' show up in the "Recently Played" section looking the same as all other songs. If I've been listening for a while then go down the recently played list clicking 'like' its hard to identify which is which.

WHAT IM CURRENTLY DOING: Right now after trashing an item I'll like the following song so I can have a visual marker then remember that that not-liked one is the trashed one. Works for the present moment but if you review after some time its easy to make a mistake and 'like' a 'trashed' song.

Thanks.

--edit--
This is specifically regarding the: "Trash Bin" Extension.

➕ Additional Information

No response

@ussher ussher changed the title A way to identify 'trashed' items in the "Recently Played" "Trash Bin": A way to identify 'trashed' items in the "Recently Played" Jan 3, 2025
@rxri
Copy link
Member

rxri commented Jan 3, 2025

As much as it in theory could be possible, it's not feasible to do because:

  1. it requires patching Queue panel,
  2. DOM manipulation isn't really great either because class names change etc and it's not something we even want to map (since it will change frequently)

honestly, this extension was supposed to be simple, not over complicated (which would be if it would be added)
closing for now, if someone works on it, go ahead i guess?

@rxri rxri closed this as not planned Won't fix, can't repro, duplicate, stale Jan 3, 2025
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

2 participants