-
Notifications
You must be signed in to change notification settings - Fork 25
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: SponsorBlock "Time with Skips Removed" and Video Speed in Right to Left Languages #506
Comments
fixed in revanced-patches-v2.166.4 |
Broken but in a different way:(I don't know if I should open a new issue or not?) |
What do you mean? Does the issue still reproduce even after updating to the latest patch? |
Yes it does even with the latest patch, I even double checked when Installing. |
When tested on another device using AOSP ROM, the issue was reproduced. Maybe.. my main device doesn't support RTL layout (but why..?) Anyway, this issue is still valid, so I'll reopen it |
Fortunately, this issue seems to be fixable. It will be reflected in the next release by the way.. This project is a kind of talent donation that goes on without any donations or sponsors. I know you're upset, but I hope you'll be a bit more polite when reporting issues. |
I'm not upset in any way? why would I be? |
fixed in revanced-patches-v2.166.10 |
is it possible for the "time with skipped segments" and speed to come after the full length as in normal (non RTL layout) ? |
broken again after being fixed in Revanced: |
Unfortunately, no further fixes are planned. Use the official ReVanced |
Type
Cosmetic
Application
YouTube 18.08.39
Bug description
In Right to Left Languages the "x" from the video speed (as in 1.0x, 1.25x...) comes after the SponsorBlock "Time with Skips Removed" instead. (screenshot below)
Steps to reproduce
Relevant log output
Screenshots or videos
What it looks like:
What it's supposed to look like:
Solution
🤷🤷🤷
Additional context
No response
Device Environment
Android 13 (One UI 5)
Acknowledgements
The text was updated successfully, but these errors were encountered: