-
Notifications
You must be signed in to change notification settings - Fork 575
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
Dislike number is on the share button #990
Comments
Can confirm on MS Edge 121. It looks like YouTube pushed a structural change that kills the dislike text container and changes the "Dislike" icon to refer to an "undefined" class, likely to mess with plugins like these |
I knew someone was gonna mention this because i have the same issue |
Same issue here on Fedora Gnome using Firefox v120 with v3.0.0.12 of Dislike Button. Hope it gets fixed before Xmas! 👍 |
Same issue here with Edge and Brave on Windows. Also on Linux Mozilla |
Can confirm, Firefox (latest) on MacOS (latest) |
same for userscript on safari |
Ditto for Firefox. |
fixed, thanks! |
I should add that the firefox addon is still on v3.0.0.12 while the latest would be v3.0.0.13 Edit: The extension even warns that there's an update but it isn't on the addon page And therefore the issue isn't fixed here |
I'm still getting this issue on Chrome 119.0.6045.200 Windows 11. Updated Chrome and reinstalled the extension and still not fixed. |
windows 10 same here Chrome 119.0.6045.200 |
I have this issue on Google Chrome: Version 119.0.6045.158 (Official Build) (64-bit) |
Have you tried to find similar open issues?
Browser
Mozilla Firefox
Browser Version
Firefox v120.0
Extension or Userscript?
Extension
Extension/Userscript Version
Version 3.0.0.12
Video link where you see the problem
Any video
What happened?
The dislike number is on the share button instead of where it should be.
How to reproduce/recreate?
I disabled the extension and the number disappeared.
Will you be available for follow-up questions to help developers diagnose & fix the issue?
Yes
The text was updated successfully, but these errors were encountered: