Browser Name: Google Chrome
Browser Version: 70.0.3538.67
Operating System: Windows 10 build 1803
Software Type: Extension
Software Version: 0.2.2
Problem Description: When using the "scroll for details" feature of YouTube which allows scrolling down for comments, etc. when in full-screen mode in conjunction with the Iridium "Play videos automatically" setting turned off, videos will pause when entering/exiting full-screen mode.
Steps to reproduce:
document.cookie="VISITOR_INFO1_LIVE=1jCNAz66qLo" then refresh browser)YouTube videos now pause when entering/exiting full-screen mode
Additional details:
The "scroll for details" feature is relatively new and has been rolling out to some users. Reddit thread about the feature
Yup youtube just push this new feature to me. Surprisingly going fullscreen from cinema/theater mode doesn't pause the video. It'll only pause when the youtube player is on default mode.
Just to chime in, I just got the "feature" pushed to me as well and am now experiencing this issue too. Interestingly, as noted by ariefpizzuti, this issue is only present for the "Default view" and not for "Theater mode."
Finally got it to happen to me, will try to find out a solution for this as soon as I can.
Seems youtube remove the words "scroll for details" when going fullscreen now and no longer pause a video while going fullscreen from the default mode.
update : It happens again
I also ran into this problem. Is there any solution?
I updated to Chrome version 71.0.3578.80 and this problem seems to be fixed. I'm not sure if it was a result of this or if Youtube made some behind the scene changes.
I believe it was a Chrome issue. The newest update had not been pushed to me yet today, and I was still experiencing the issue. I manually updated Chrome immediately after testing, and now the issue is completely gone!
I haven't updated my browser yet but that would explain why I haven't been able to get it to happen on Firefox all this time.
Definitely a Chrome issue, can confirm 100% as I was dealing with the same issue. Just manually updated to v71, hoping that will fix the issue.
Alright, thanks everyone for the help. I'll close this for now since it is related to a browser issue and not the extension.