-
Notifications
You must be signed in to change notification settings - Fork 27
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 - Overlay Buttons): When the patch option Bottom margin
is 0, all player bottom buttons are hidden
#2720
Comments
Does the issue still occur even if you exclude the Also, have you changed any patch options for the |
@inotia00 I didn't change any patches options in |
Player Components
& Overlay Buttons
): All buttons just above the seekbar do not appear
It may be due to the recently merged PR inotia00/revanced-patches#129 There was no issue when I tested it on my device, but I didn't know there was an issue on other devices. I'll revert the PR. |
What options have you modified within the |
Yep, as I thought. Reverting the commit is not necessary. The problem stems from the bottom margin being set to 0dip. Fixing this (bottom margin) should resolve the issue; apart from that, it functions correctly. |
Bottom margin
is 0, all player bottom buttons are hidden
… is 0, all player bottom buttons are hidden inotia00/ReVanced_Extended#2720
Reflected in revanced-patches-5.3.1 |
Type
Error at runtime
Tools used
RVX Manager
Application
App version: 19.44.39
Patches version: 5.3.1-dev.4
Bug description
When I enter any video, all buttons just above the seekbar do not appear - more precisely: timestamp, additional info to them, any overlay button, fullscreen button. Naturally, I didn't touched any of these options after install. "Widoczny/widoczne" means "shown", "ukryty/ukryte" means "hidden".


Error logs
Solution
No response
Additional context
No response
Device Environment
Phone: POCO X6 Pro 5G
Android: 15
System version: 2.0.2.0.VNLEUXM (EEA Region)
Acknowledgements
Experimental Flags
.The text was updated successfully, but these errors were encountered: