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

Play all button in feed/What's new #3362

Closed
ghost opened this issue Apr 4, 2020 · 12 comments
Closed

Play all button in feed/What's new #3362

ghost opened this issue Apr 4, 2020 · 12 comments
Labels
feature request Issue is related to a feature in the app feed Issue is related to the feed GUI Issue is related to the graphical user interface

Comments

@ghost
Copy link

ghost commented Apr 4, 2020

Play all button in custom Youtube feeds above the menu on the right / Background listening or video watching options

Thanks
Onder

@Stypox
Copy link
Member

Stypox commented Apr 5, 2020

Could you provide some feedback in #2583? This will be implemented at some point ;-)

@Stypox Stypox added feature request Issue is related to a feature in the app GUI Issue is related to the graphical user interface labels Apr 5, 2020
@wb9688
Copy link
Contributor

wb9688 commented Apr 5, 2020

We should indeed add our playlist controls to the feeds.

@wb9688 wb9688 added the feed Issue is related to the feed label Apr 8, 2020
@TippyLion28

This comment was marked as duplicate.

@litetex litetex changed the title Feature Request: Play all button in custom feeds Play all button in feed/What's new Feb 26, 2022
@vozer
Copy link

vozer commented Mar 5, 2022

Addendum:

When I am watching my feed I would like be able to click on video and select "play list from here", then x number of videos should be queued as a play list and played after each other.
Better than play all because you can select where to start

@komals1
Copy link

komals1 commented Aug 16, 2022

is it possible to select multiple videos from feed at once and then enqueue them all to play

@SameenAhnaf
Copy link
Collaborator

Closing in favor of #5737

@TippyLion28
Copy link

Why close? It's not exactly a duplicate.

@opusforlife2
Copy link
Collaborator

Same difference.

@TippyLion28
Copy link

@SameenAhnaf what was the rationale behind closing #5737 in March, then reopening it in December just to close this one?

This issue was opened before yours, so surely if the two issues are asking for the same thing then yours should have been marked as a duplicate in the first place?

@opusforlife2
Copy link
Collaborator

The more general/better explained issue tends to be preferred if it is opened later.

@TippyLion28
Copy link

Understood, that makes sense.

My only concern is how long #5737 will survive before @SameenAhnaf decides to close it randomly. I've had it before where they've closed my issue as a duplicate of theirs but then closed their issue as completed a few months later even though the feature was never implemented. :/

@opusforlife2
Copy link
Collaborator

@SameenAhnaf Make sure you never close an issue if another issue was marked as its duplicate, without ensuring that yet another issue for the same feature/bug is opened, or already exists and isn't closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Issue is related to a feature in the app feed Issue is related to the feed GUI Issue is related to the graphical user interface
Projects
None yet
Development

No branches or pull requests

7 participants