Issue metadata
Sign in to add a comment
|
I can no longer autoplay youtube videos when opened in background tabs
Reported by
nicspla...@gmail.com,
Nov 6 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36 Example URL: www.youtube.com Steps to reproduce the problem: 1. Go to chrome://flags and set the Autoplay Policy to "No user gesture is required" and restart chrome 2. Navigate to youtube, and open a video in a new tab (right click on a video, open in new tab, or middle-mouse click to open in new tab) 3. Observe the opened video does not play in the background until you click on the tab and bring it into focus What is the expected behavior? -With the autoplay policy flag set to "No user gesture is required", new background youtube tabs (and other media tabs) should not require interaction to start playing. -With the autoplay policy set to anything else, user gesture should be required for media to play. -This behaved as expected in chrome versions older than version 59, where this chrome flag was actually named "disable-gesture-for-media-playback" and I was able to open youtube videos in background tabs, where they would autoplay without me clicking on the new tab. What went wrong? The autoplay policy flag now seems ineffective, especially compared to chrome versions previous to version 59 where the flag was named "disable-gesture-for-media-playback" and I was able to open youtube videos in the background, and they would autoplay without any extra input/gesture Did this work before? Yes Is it a problem with Flash or HTML5? Both Does this work in other browsers? Yes Chrome version: 62.0.3202.75 Channel: stable OS Version: 10 Flash Version: Contents of chrome://gpu: I'm re-opening this issue. Stop marking it as duplicate, or wont fix, without commenting or telling me why. I'm extremely frustrated that I have tried over and over and over and over and over AND OVER again to get this resolved and I keep getting silenced. The bug I previously opened for this issue WAS NOT FIXED, WAS NOT RESOLVED, AND HAS NO WORKAROUND. As I see it this is an outstanding issue that needs to stay open until it's actually resolved. Someone please help me out for once
,
Nov 6 2017
The bugs are marked as duplicates because they are duplicates: it's the same issue with the same resolution (Won't Fix in this case). You filed the same bug multiple times and the answer was provided in https://bugs.chromium.org/p/chromium/issues/detail?id=771304#c3 Opening new bugs will just spam developers who will have to realize it's a duplicate while getting you no closer to the Chrome behavior you desire. If you disagree with Won't Fix, feel free to continue conversation on that bug. Since the default behavior has been changed more than 2 years ago, I don't see it being reverted or an alternative supported without strong user demand. Perhaps, a better path forward is to push for this to be added as part of the new autoplay policy: https://developers.google.com/web/updates/2017/09/autoplay-policy-changes https://blog.chromium.org/2017/09/unified-autoplay.html
,
Nov 6 2017
This is so stupid, the code keeps progressing to more and more unwanted behavior and I haven't brought it up until my workarounds no longer were effective. So just because I'm supposedly the only one with this issue it makes it insignificant and meaningless. Thanks I guess |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nicspla...@gmail.com
, Nov 6 2017