-
Notifications
You must be signed in to change notification settings - Fork 567
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
Save & Share Buttons Go Missing #1084
Comments
that's because of the issue #1074, the extension now hides the "extra" buttons so the youtube page does not break browse comments in the issue to see why is this extension now doing that |
Oh okay. The 'KellyC Show YouTube Dislikes' extension does not have this same issue. All the "extra" buttons show up on the YouTube page perfectly fine, and the YouTube page itself never breaks. |
Just want to inform that KellyC do have the same issue as reported here NC22/KellyC-Show-YouTube-Dislikes#28 I don't know if they will fix it as the last commit in their repository is 4 months ago |
Have you tried to find similar issues (open or recently closed)?
Browser
Mozilla Firefox
Browser Version
129.0.2
Extension or Userscript?
Extension
Extension/Userscript Version
3.0.0.17
Video link where you see the problem
https://www.youtube.com/watch
What happened?
The row of buttons under the video player like Save and Clip sometimes get automatically collapsed/redirected into the overflow menu when Return YouTube Dislikes is enabled.
When this happens only the Share button in the UI remains visible on-screen. A simple refresh of the page brings back the Save & Clip buttons, but it' annoying having to do this to bring the buttons back.
This issue does not occur when the Return YouTube Dislikes extension is disabled, or when using the KellyC Show YouTube Dislikes extension.
How to reproduce/recreate?
Click a video thumbnail from your home feed or subscription feed, and once the https://www.youtube.com/watch page loads up - the Clip & Save buttons are missing.
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: