Issue metadata
Sign in to add a comment
|
re-enable autoplaying media in background tabs, or make user configurable, or make flag effective again
Reported by
nicspla...@gmail.com,
Jan 11 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 Example URL: Youtube Steps to reproduce the problem: Navigate to youtube.com, and open a video in a new tab. Note the video does not autoplay until you click the new tab you've opened. What is the expected behavior? Media should autoplay. This used to be default behavior in chrome. Changes were made to remove this behavior, but an autoplay flag was introduced so users could still get this behavior back. The autoplay flag is now ineffective and users have no way of getting the desired behavior What went wrong? The autoplay behavior was removed. A flag was put in to allow us to re-enable it. The flag was later broken. Bugs were opened but they keep getting closed as wont fix or they never get any attention and get ignored. Did this work before? Yes 60.0.3082.0 Is it a problem with Flash or HTML5? Both Does this work in other browsers? Yes Chrome version: 63.0.3239.132 Channel: stable OS Version: Any Flash Version: Contents of chrome://gpu: Till 60.0.3082.0 we have gesture-requirement-for-media-playback flag and on disabling it we used to have audio playback on background tabs as well. From 60.0.3083.0 flag is not seen and autoplay policy flag is seen and on enabling/disabling it unable to listen any audio playback on background tab until you navigate to that tab. This change is responsible for the flag being replaced and broken; https://codereview.chromium.org/2845973005 Understand that I am not necessarily asking for an experimental flag to work. What happened was chrome used to autoplay without any flags, but later flags were introduced alongside the change to no longer autoplay media. When that flag was first created, it let us get the old autoplay behavior back. Now the flag was replaced with the useless current version that is no longer an effective workaround. I seek any sort of workaround, alternative, or anything to get this behavior back. Feel free to sort through issues I have opened, you can see I've been trying for a LONG time to get this fixed and no one is helping me
,
Jan 12 2018
nicsplatts@ Thanks for the issue. This issue looks similar to issue 799136 . Hence duping this issue. CC'ing mlamouri@ for more updates on this issue. Thanks..
,
Jan 12 2018
Thanks for cc'ing the dev responsible for this being closed over and over as won't fix. I can't wait to see no progress as usual. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Jan 11 2018