UserAgent: 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.com

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?
With an effective flag, or a workaround, for media to autoplay when opened in a new tab without gesture input.

What went wrong?
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

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: 

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.

I also need to note chromium bug tracker user mlamouri@chromium.org absolutely should NOT be assigned to this case, as they have proven to repeatedly close this issue as won't fix and refuse to provide us with a solution or any help.  I fail to see the difficulty in helping the users get what they want, not what the devs want.

 This single dev keeps single handedly closing all these bugs users keep opening asking to fix this. This used to be a feature and it was taken away from us.