🐞 Force auto-play off prevents me from playing the video
Concise Description
I can't play videos with the Force auto-play off setting even after hitting the play button.
I have some privacy settings setup on Mozilla Firefox, they may or may not be interfering.
Browser/s
Firefox
Other Browser:
No response
'Steps to reproduce' - Which of our features is required for the bug to happen?
Force auto-play off
Since when?
Since I installed the extension
Does the bug still happen when you log out of YouTube?
None
..No? Then please paste your yt.config_.EXPERIMENT_FLAGS. Twice (With the error & Without)
No response
Are any errors or related log-messages shown in the Browser-Console? (F12)
No response
Tested as the only active extension? (incognito mode or another browser users):
None
Expected preferred behavior:
No response
ImprovedTube Version
No response
Your Settings (From the Extension's ⋮-Hamburger menu > Settings > Backup & reset > Export settings)
No response
Your YouTube-Document
No response
OS / Device:
No response
hey i would like to take up the issue.
please reply asap so that i can work on it and give a pull request as soon as possible
is this the exact issue are you facing The extension has a setting called “Force auto-play off”, meant to stop YouTube videos from starting automatically. However, this setting is over-aggressive — it completely blocks playback, even when you manually press “Play.”
is this the exact issue are you facing The extension has a setting called “Force auto-play off”, meant to stop YouTube videos from starting automatically. However, this setting is over-aggressive — it completely blocks playback, even when you manually press “Play.”
Exactly
i am working on it right now will give you a pull request once done
I was refreshing the tab and immediately pressing play before the mechanism kicks in before discovering that the problem is with that setting
i am working on it right now will give you a pull request once done
I'm not familiar with pull requests or working with Git in general. I'm learning about it right now
you can a video/screen recording for the exact thing to be done and how it is working right now is it possible??
I activated it again to reproduce the problem but it worked correctly this time for some reason. I think there is no bug and just something from my end. I'm sorry for taking you time. You can close this issue and if the problem reappears later I will let you know. Thank you
no worries
Here is a screencast of the problem
Just popping in to report I also experienced this problem.
I believe this is one of those "Variable" bugs that does not have a reliable way of reproducing on all devices. What I'm saying is that a way of reliable reproducing this bug on one device will not work on another device, even if said device is identical to the first device.