-
-
Notifications
You must be signed in to change notification settings - Fork 322
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
bug(YouTube - Spoof client): Playback speed flyout menu is missing #3203
Comments
There is no playback speed button in the player. Playback speed is in the flyout menu. |
Yes I am aware of that. It is not appearing in the flyout menu, even when it is enabled. I am not the only one facing this issue, a lot of users mentioned this on reddit too. |
Turn off |
I'm able to reproduce this just now. Flyout menu is missing the speed option, for both spoof client types. The speed button on the "premium controls" (premium feature) is present, but it does nothing and opens an empty flyout menu. |
I'm experiencing this as well. When I turn |
This is one of the limitations we can work around with with #3197. I am not sure why the player request causes these issues because the player only returns player data and not layout instructions. What can be done is set the response type to json, check if it contains anything interesting in this regard. If it does not, that means we don't only touch /player requests. Perhaps YouTube is also caching objects so when we modify them with a hook, they may be used in a other request. Perhaps after the request is done, we could reset the fields we change and see if that makes a difference |
Moving to #3208 |
Bug description
Playback speed button no longer shows up in the flyout menu. There is no way to change it currently other than by setting it in Revanced - Video - Default Playback Speed.
This issue appeared after updating from 4.7 to 4.8. No changes in default patches, and cache was cleared. The option to show playback speed was enabled and disabled too.
Error logs
No response
Solution
No response
Additional context
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: