-
-
Notifications
You must be signed in to change notification settings - Fork 542
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
IT/1959 Loop/Repeat Parity #1990
IT/1959 Loop/Repeat Parity #1990
Conversation
…functionally linked when both active.
hi @kjonathan024! thank you! querySelector by class can be "slow. (Might only be worth considering because it is enabled by default and can run billions of times). Generally one could use getElementById. But we can also just call it on click only, and then we can specifically check our settings in that are loaded already, to know if the other button is enabled ( just added to #1504 :
|
… by id for this button.
hi @ImprovedTube ! Thank you for your comments, I have made appropriate changes based on your recommendations. |
hi! thanks @kjonathan024, hope you like the 4 commits above and they don't break anything.
|
@ImprovedTube Thank you for your guidance and support! Glad to be able to contribute to your project. From the testing that I did, it seems that I remedied any small bugs that happened because of the change. |
I just encountered the same issue. |
Improved the sync of the repeat and loop buttons to be visually and functionally linked when the user turns both buttons on. Before, I noticed that when one was set to on and the other was then added, the visual indicators of if the video would loop or not was indiscernable. I fixed this by detecting if the other button was active and then setting their opacities to be the same based on the current setting of the video (if looping or not). I did this through the onClick functions for each button respectfully, as well as adding an if statement check when the button is first added to ensure it is visually and functionally in sync.