New issue
Advanced search Search tips

Issue 821444 link

Starred by 7 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

we used to be able to autoplay media in background tabs! now we cant get this behavior back

Reported by wutanghome@gmail.com, Mar 13 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36

Steps to reproduce the problem:
an insane amount of users keep opening bugs asking for a fix for this, so stop trying to ignore us. we used to be able to open, for example, youtube videos in a background tab and it would just play by itself without interaction. that broke and we had to use a flag to work around it, but the flag doesnt work anymore either and we're screwed.

specific devs keep closing thee bugs as wontfix when it starts getting traction. can someone please help the mass amount of people who have been asking so long for this?

see  bug 816547 

What is the expected behavior?
see  bug 816547 

What went wrong?
see  bug 816547 

Did this work before? Yes 

Chrome version: 64.0.3282.186  Channel: n/a
OS Version: 
Flash Version: 

play fair! stop closing these bugs! we want a fix! if you are going to close this and not provide a solution you are the problem
 

Comment 1 Deleted

how incredibly frustrating would it be to use something as it is for years and years and years (literally since the product's conception) and after all that time you can no longer use it that way and the developers of it said "we dont think about what you want, bye" and so much as not provide any help whatsoever

its a sad time yeah
a sufficient amount of users have asked for this back in  bug 816547  and  bug 728108 
very difficult to continue using chrome the way it is now but all my sync data is here, I dont want to switch if I dont have to :(
More comments in  bug 728108  asking why this keeps getting unresolved


Components: Internals>Media

Comment 7 by ash2...@gmail.com, Mar 23 2018

I'm greatful for anyone that wants to help fix this issue (thats also impacting me too) but want to also strongly recommend other users stop with personal attacks on devs as its not helping our case. 
I would be grateful for any of the following:

-Since autoplay was the default behavior, reenabling it
-Since autoplay was eventually disabled, but still available as a flag, add back the original flag that let us re-enable it
-Since the autoplay flag was replaced with one that's no longer effective, make the new autoplay flag effective again
-Mark as resolved wont fix but provide a sufficient resolution or workaround to this issue

None of these have been satisfied and there continues to be a single point of failure for this, hence the finger pointing and attacks towards a specific developer. Not by me, but complaints from multiple users here. 

When I emailed this chrome developer directly to address the issue (per their request) we reached no satisfactory resolution. They stopped responding to my inquiries and have been silent.
Please re-enable the flag that allows users to autoplay videos in a background tab.

My only guess as to why this is happening only in this browser is google owns YouTube, and if they want us to click on the tab to see the next pre-roll ad before the next video.

Comment 10 by ash2...@gmail.com, Mar 27 2018

I totally understand if that's the case and Google wants to maximize genuine ad impressions, but in my case I have a YouTube Red subscription so there are no ads. If this is the only reason, I wish they would at least give paying customers a way to enable the feature. Otherwise, the only logic I can think of for why this is such an issue is that they are trying to be helpful in making sure people don't get bombarded with autoplaying videos when they don't want to - in which case I don't understand what the logic is for taking the flag functionality away as a work-around for tech savy people that understand the risks and are not only willing, but begging to have that functionality.
I also pay for youtube red, and don't have any ads. I pay for youtube red to have a music experience, and that includes opening things in the background without having to interact with them (because its music, not a video I want to watch)

I no longer wish to pay for youtube red if I can't use it the way I used to. 

Comment 12 by ash2...@gmail.com, Mar 27 2018

Music, either through YouTube or other services is definitely my own primary motivation for wanting and previously using this feature. Speaking of paying for things, my Google Home doesn't stop between every single song and ask me, using a separate device with a screen, to verify if I want to start playing the next song, so why is Chrome forcing us to do this? 
If there is some legitimate technical reason why this is the only browser on the market to force users into this situation I would be happy to hear about it.
after this im . considering stopping my youtube red family subscription, switching to firefox (gross, but yeah) and using adblock. its free 


Status: WontFix (was: Unconfirmed)

Comment 15 by ash2...@gmail.com, Apr 11 2018

Why?
Time to open another bug. This is so sad...going to be reporting these devs that maliciously close these bugs

Comment 17 by ash2...@gmail.com, Apr 11 2018

I dont even care that the bug wont be fixed i just wish they would tell us why.
Silence is the most convicting display of their character. I've not gotten any responses from the direct emails to them either. 

Who holds these guys accountable? How do we escalate this?

Sign in to add a comment