-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Return to Play Queue screen from video details #7208
Comments
Wouldn't #5235 solve the bug for you? |
Yes, it would. However, that is a feature request for something that does not yet exist in NewPipe, and to be honest I think the current implementation is fine. What I'm asking for is a bugfix for a feature that exists today. If #5235 gets implemented, this issue is redundant. However it has not been implemented, so this issue stands. |
This comment was marked as resolved.
This comment was marked as resolved.
@yashpalgoyal1304 It works fine for me. Please check again. @TippyLion28 It could lead to complications, as currently the main player shows the play queue already. So you would have access to the same play queue using 2 different actions. |
The video info screen does not show the play queue when the background player is being used. If I do Background Queue > Long press a video and select "Details" > then press the hardware back button on my device nothing happens. If I press it again it just minimises the video info screen. What I am proposing is that pressing the hardware back button should send you back to the background play queue |
Ah. That makes sense. Please update your description to say that. |
Checklist
Steps to reproduce the bug
Fire up the background audio player and open the Play Queue screen from the notification. Long-press a video and tap "details". Now swipe down the video screen as to minimise the video details.
Actual behavior
App returns to the main NewPipe window.
Expected behavior
App should return back to the Play Queue.
Screenshots/Screen recordings
Can provide a screen recording if necessary.
Logs
Device info
The text was updated successfully, but these errors were encountered: