media not playing in background tabs
|Reported by sweetmon...@gmail.com, May 31 2017||Back to list|
UserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.7 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Open media (video, audio) in a background tab. 2. 3. What is the expected behavior? The audio/video should play if the chrome://flags option "Optimize background video playback. Mac, Windows, Linux, Chrome OS, Android Disable video tracks when the video is played in the background to optimize performance. #disable-background-video-track" is disabled. What went wrong? This issue seems identical to issue 544723 . Has the patch lapsed? https://bugs.chromium.org/p/chromium/issues/detail?id=544723 Did this work before? Yes https://chromium.googlesource.com/chromium/src.git/+/b125a7be15ab35b07f11bf252da1d52bf1a32e06 Is it a problem with Flash or HTML5? N/A Does this work in other browsers? N/A Chrome version: 60.0.3112.7 Channel: dev OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 26.0 r0 Contents of chrome://gpu: Chrome browsers on other machines seem unaffected.
Yes, that's it. But could this be an option in Chrome ? It's a pain in the * for every audio website to not be able to autoplay the next track. (don't know how Soundcloud manage to do it) I lost a big slice of my visitors since we can't autoplay anymore.
This should only apply to tabs that have not been playing in the foreground before. "next track" feature should not be impacted by this. If it is, can you give me steps to reproduce and I will have a look?
Of course, have a look at this page : http://www.spiff-radio.org/wpsstm_live_playlist/fip/ When tab has not the focus, tracklist do not play next track.
I don't have a problem with autoplaying playlists. Youtube, soundcloud, and Spotify all work in that regard. However, for example, if I right click a Youtube video and select "open link in new tab," it does not play until I visit the newly opened tab. This behavior was a new "feature" to Chrome dev 48.0.2535.0 and a flag was introduced in 48.0.2563.0 to disable this behavior according to issue 544723 . https://bugs.chromium.org/p/chromium/issues/detail?id=544723. This flag was removed in dev 60.0.3112.7 and subsequently in production version 60.0.3112.101. The flag "Autoplay policy Mac, Windows, Linux, Chrome OS, Android Policy used when deciding if audio or video is allowed to autoplay. #autoplay-policy" does not have any affect on this behavior, and indeed, firstname.lastname@example.org, indicated that the flag might be broken. I would like to be able to have the option to autoplay media in new tabs again, or should I consider a different web browser?
re #13: so... the reason this is happening is because some of your playback comes from YouTube iframes that you are injecting in the page and the check we have is per frame. It's working fine when you only use the SoundCloud API. dalecurtis@, do you remember why this is checking on the specific frame instead of the WebContents except that because the check is on the renderer? re #14: the behaviour you see is working as intended and the autoplay policy isn't meant to change it. I'm afraid that Chrome can't have an experience tailored to every single use cases :(
I get your point, but it seems asinine that a function that used to exist was taken away and results in a poor user experience. Can I at least request that this option be added back to Chrome?
@mlamouri: Yes it's a renderer only check currently to avoid any round trips to the browser. It seems this is a regression as indicated by the summary in c#14. As I submitted the original workaround I believe UX should exist for disabling this functionality if users desire. So the chrome://flags option for autoplay policy should be fixed to include this case. Back to you and +dahlke to make the final call.
Issue 771304 has been merged into this issue.
for the love of god, please give me back control over this like I had before. I need autoplay for background tabs
" So the chrome://flags option for autoplay policy should be fixed to include this case." i know this is a huge request, but the correct behaviour for this would be a popup (like the geolocation popup) asking to allow the website to autoplay stuff
Another prompt (like geolocation or notifications) may be useful. Great for experinced users, but some less experienced users will be confused first/again. I agree with this idea and I'm suggesting to consider it. ... meanwhile please make that bloody flag work again! This is crucial. Thanks
Additionally, the --ignore-autoplay-restrictions switch does not affect the aforementioned behavior.
#15 "so... the reason this is happening is because some of your playback comes from YouTube iframes that you are injecting in the page and the check we have is per frame. It's working fine when you only use the SoundCloud API." So you mean that if I inject all the Youtube iframes when the user is on the page, it will work ? But what if it requires to load 100+ youtube iframes ? Won't it be very heavy in terms of ressources ?
The NextAction date has arrived: 2017-11-13
Would love to see the flag come back so I can turn on the behavior that I've always had before this was changed. Please.
What is "NextAction" ?
Any updates on this?
eager to see this get resolved, but in the meantime I must switch to [INSERT ALTERNATIVE BROWSER HERE] because the impact this change had on my workflow is detrimental and too frustrating
As mentioned in #13, Chrome does not intend for chrome://flags to be user facing options and is meant for testing/experimenting with features. Blocking playback until a tab was focused is a feature of Chrome for which we do not intend to have a user facing setting. The issue with the radio website injecting iframes is something worth opening another bug for, however.
So what is the recommended workaround to achieve the desired behavior of how the browser used to work? Not intending flags to be user facing seems like a flimsy argument when there was a flag that did exactly what I want. Call it a setting if nomenclature is all you're worried about.
This is REALLY disappointing. Guess I've just to put a HUGE POPUP on my website to tell visitors to use another browser.
Are you kidding me? Why not give us the freaking ORIGINAL behavior back instead of taking it from us, then taking the ability to enable it.
I would like to hear what I'm supposed to do to workaround this nonsensical behavior
@mlamouri unacceptable without a work around
Regardless of the "flags being experimental and not intended to be user facing" none of us are fighting that, we are fighting for the fact that, at one point, the default behavior was autoplaying media. Suddenly this changed to default not play, but a flag was introduced to switch this behavior. Now, you want to change the default behavior, take away our flag to change it back, and tell us no way how to get this back??
1/2 year and no solution... Is it really that hard to just do your job and fix something that is broken? We don't wanna to be a standard option but to be an option in the flags for developers. Removing this feature is pushing me one step away from chrome... Edge doesn't have this problem.
@bob no other browser I've tested (firefox, IE, edge, opera, and old versions of chrome) has this issue, it's purely a code change on chrome and I cannot get anyone to reverse this change or add a way for us to get the old behavior back
Opera has this issue too (at least the developers versions).
We still want this fixed!
Issue 787568 has been merged into this issue.
What a load of bs. Give us a fix
What is the workaround
That "featured" was really annoying. However that flag fixes it (using --ignore-autoplay-restrictions) https://www.chromium.org/developers/how-tos/run-chromium-with-flags although it may cause other problems as it cancels the block altogether...
I will have to try it again, since it's never worked the way you described. Media never autoplayed no matter what that flag was set to, which is unlike the behavior of the previous autoplayed flag
Agreed. The --ignore-autoplay-restrictions switch did not work for me when I tried it.
I don't know guys, I just followed those instructions. I added --ignore-autoplay-restrictions to my chrome.exe and it worked (I also have Autoplay policy --> No user gesture required) ... Windows 10 Pro, 64. Chrome Version 62.0.3202.94
I don't think that flag has the same purpose than the old one, but I can be wrong. Anyway I had a try and doesn't work here either. 2017-12-13 17:26 GMT+01:00 8odo… via monorail < email@example.com>:
Even if that did work, which it's not for me, how would I go about doing that on Mac OS X? 8odo...@gmail.com
Anyway no one regular user will do that complicate trick to surf a website. We need something easy to use for visitors. 2017-12-13 17:27 GMT+01:00 nicspla… via monorail < firstname.lastname@example.org>:
Well unfortunately email@example.com refuses to help us at all, they will continue to close these issues as wont fix and screw us who want this back, all while not giving us any alternative solution. I will keep opening new issues until this is resolved if I have to.
Still no support on this issue?
Give up. They have decided. They're not going to fix it. You're just wasting your time.
I refuse to give up until the better interest of the user is considered, not the will of the developers.
Comment #15: "I'm afraid that Chrome can't have an experience tailored to every single use cases :(" It can, and very easily. Simply give us back the original autoplay behavior, or fix the flag you gave us when you took that behavior away, or make the new autoplay policy flag effective. I don't see what the difficulty int his is, unless this is too hard of a task for you to re-implement what was once existing behavior. You've gone from making both style of users happy, to cutting some out, and telling them to eat it.
Still seeking a resolution
#metoo 2017-12-15 18:15 GMT+01:00 nicspla… via monorail < firstname.lastname@example.org>:
Removing the 'Disable gesture requirement' was a really stupid choice. It effectively breaks Youtube playlists. It's like Google wants me to switch to one of their competitors? Nic - I really appreciate your persistence with this. This has annoyed me for months too.
@67 I will keep this up until it's fixed. @mlamouri listen to the users, and fix this. We are still waiting and I'm happy to continue asking you for the rest of your chromium developer life.
:) we all will continue to ask over and over and over and over again until we get what we all ask for. :) :) :) we suggest listening to the users!!!!
I am still seeking a resolution, whether it is to bring back the flag, or make the existing one effective, or bringing back the original autoplay by default behavior.
...or update the Youtube API. 2017-12-19 18:32 GMT+01:00 nicspla… via monorail < email@example.com>:
@firstname.lastname@example.org still waiting for any input. No one who calls them self a real developer would pull this act on their users. We'll be here when you want to consider us!
Would be nice if the flag actually functioned as designed, or if the auto-playback was reverted to previously.
Merry christmas. @email@example.com fix this
hi please fix thanks
please provide a fix or solution thanks
I think for google this isn't bug, they want this behaviour
I can't find a perspective where this isn't a bug or desirable behavior. The flag is ineffective so it screws a large portion of users who liked autoplaying. Even before the flag, it was default behavior to autoplay. Why change it and take away the user's ability to tweak it back?
Still waiting to be proven wrong my mlamouri. I see more and more bugs being opened asking for this to be fixed and they are stopping any progress
Still waiting to see this fixed
Does anyone have a workaround for this, it's really annoying that I can't just effortlessly listen to YouTube in the background anymore...
>breaks autoplay >breaks the flag >says its for the best use case >breaks youtube preventing more than one video simultaneously playing (like, what? seriously you claim not having autoplay is for the best then this happens??) >tells users they are screwed >offers no support or workaround >closes all the bugs from people asking for this back gg mlamouri, stellar
Nothing grinds my gears more than feature regression. We've had autoplay since the incarnation of chromium and now its removed with absolutely no way to reactivate it. Completely screwing with a lot of peoples user flow and any mention of it is being suppressed. I can't help but think this is some sort of ploy to increase ad impressions.
hi i opened a new bug cause there seems to be enopugh demoand to fix this vote here bug 816547
Do we need Mark Lamourine (mlamouri) to solve this issue? What about to bypass him by someone who cares? Is it possible to track down the original author or piece of code, make a patch or push a PR?
Issue 816547 has been merged into this issue.
Mark, why do you keep fighting users on this and marking it wontfix without any sort of explanation? Why do other developers keep passing this issue back to you, knowing that you aren't going to do anything? Why is it such a problem to fix the flag to work as this issue originally noted? Is this WontFix supposed to mean that something isn't actually a problem... or does it just mean that you don't want to actually do the work?
New bug opened! bug 821444
I also would really really love a way to enable background autoplay of youtube videos. Please!!
@92 Ryan > Not just youtube folks, this affects every site and not just <video> tag but also <audio> ... so even intranet tools with sound notifications are screwed :/
gonna be cancelling my youtube red over this since I cant play my youtube videos in the background anymore. taking wutangs idea and using firefox + adblock
@firstname.lastname@example.org Can you provide any feedback on why Mark keeps marking this WontFix and won't explain why we shouldn't be able to have control over whether we want to play videos in the background? Do the Chromium developers actually believe that the "flag" to control this is working, and there really isn't a problem? Because that flag doesn't work anymore for any of us. Why can't we get an explanation yet you're here making comments that have nothing to do with the problem or why Mark is refusing to consider fixing it?
Also why is this marked OS Windows when it also affects Linux and probably Mac?
@97 you can only select and file under one platform.
and good luck getting anyone to respond to this anymore. too bad there is no way to hold these devs accountable while they crash and burn the chromium project
new bug 834871
Issue 834871 has been merged into this issue.
in response to becca, opening another bug thanks!
created an account just to come comment on this issue. what a disgusting display by the developers on this site to pull these stunts. these peoplewant something and you are giving them the middle finger.
these users depend and rely on you to help and you are screwing them over. what do you expect them to do
Becca you are amazing! You don't bother responding to anyone's concerns, but you have time to sit and snipe bugs being opened and closing them within minutes. Keep up the great work, your priorities have been made clear.
shoot me an email if you would like me to privately send you new bug numbers as they are filed. obviously sharing it here results in them getting closed :( will be creating a few accounts to shake these bad devs off us. and if they choose to waste their time trying to hunt down the bugs to continue maliciously closing them, that's their time wasted not doing their "job"
Wow. Just.....wow. Consider fixing the bug. To repeat my input from another bug; "...Understandably this is related to an experimental flag, however, at my software company, when we make changes that affects a user's workflow, we have ways to let users revert to the previous one so the user is happy, not the developer. So while flags are experimental, it appears that making it actually work the way everyone is asking it to (as in controlling the youtube autoplaying) would fix both sides of users wanting and not wanting autoplay when it happens. I don't see what is so difficult about this issue other than simply fixing it. That's my input. Thank you."
I found a sufficient amount of users who are very upset about this autoplay change one way or another. Read the comments at the end of this developer update post https://developers.google.com/web/updates/2017/09/autoplay-policy-changes We need a setting!
oof, I read that dev update and was completely baffled. Why did they create a whole complicated backend systems for trying to guess at what the user wants rather than just implementing a simple On/Off switch... this is absurd.
I will save you guys the time and include a few of the choice comments here. Almost every comment on the blog post that was for the autoplay policy changes is complaining about this change one way or another. The majority of users are asking for control over this setting! Here are a FEW of the comments on the blog post about the autoplay policy changes that stuck out to me: 1: “Same as many others. This worked for about a day before these sites seem to have found a way around it.” -So the main debate about how this is the best user experience doesn’t hold up when the changes are only half-effective anyways. 2: “I’ve had the new Chrome for several days now. On the first day, the mute autoplaying videos feature seemed to work. But now, I've got more loud, un-muted, autoplaying videos than ever. This feature is NOT working.” -Again, the new policy doesn’t even fully work. I think we get the idea that this feature doesn’t work correctly in the first place. 3: “We are developing an offline exhibition for children, and we need to auto play videos. Is it possible to some how make it” 4: “I can definitely agree with the masses. This is a terrible update. Not that it isn't useful ( it can be ), but why not add a "Never play videos" and "always play videos" option. You have a "Document user activation required" flag that does absolutely nothing from what I've seen.” 5: “Audio has stopped playing on several websites - 20th April 2018. Presumably something auto updated on Chrome overnight and fouled things up. I uninstalled Chrome then reinstalled it - no difference. So I've given up on Chrome after about 4 years on my Windows 10 PC and have gone over to MS Edge where autoplay of audio works fine.” 6. “Bye bye Chrome and welcome FireFox. Installed and ready. Autoplay is working fine.” 7. “I am considering disabling Chrome as my preferred browser... Especially if I have to go to Firefox just to watch a FREE TV Channel and cannot simply set my own personal preference to autoplay videos. Keep it simple Chrome! Seriously. WHY complicate things for what should otherwise be simple?” 8. “Hi so my video that is mute works everywhere else but on chrome. There is no sound to begin with and I mute it. I get this error: "Unmuting failed and the element was paused instead because the user didn't interact with the document before. How can I fix this“ 9. “I really hope they keep the flag to disable this forever, otherwise this will kill kiosk and unattended systems that run on chrome.” 10. “This new policy just broke the product our company provides which is an unattended media player with custom contents, this isn't cool google…” 11. “I would like videos in Yahoo View to play. I can play them in Firefox. They had been working fine in Chrome until version 66.0,3359.117 and now I get a message saying Sorry you browser blocked our content playback. You should disable the content blocker of browser and enable autoplay if you want to watch this video. Then it has instructions for Safari. I would like to continue using Chrome as my preferred browser, but this conflict send me to Firefox. How do I enable a content blocker I never disabled????” 12. “Good morning. We are a company who display scheduled digital content over web browsers. We are very affected by your new policy and we would like to know, what are the alternatives to the enterprises who use the autoplay as a business rule. I mean, this is one requirement from our customers.“ 13. “how do u autoplay videos on site i play ffs and someone told me that chrome dont auto play FFSNG shared a link to the group: FFSNG Lounge. 12 hrs · “ 14. “This is the stupidest update of a relevant software in a while. It deliberately choose random number of requirements, which are mutable over time, to destroy consistent deliver of media. It breaks the implementation trust, and overall user experience. Absolute regression.” 15. “Absolute shit update” -personal favorite 16. “How do we white-list a domain ? we develop unattended kiosks and queue systems, need audio to work” and a reply to this comment from another user who says they need the same thing 17. “What a horrible documentation. Where do I have the option to never play videos or audio?” 18. “Well, that's not very friendly for internal system. Some think client app use autoplay for training video, etc... I am not sure one size fit all strategy is the best the brilliant mind @ Google are able to come up with. Looks like Chrome is now matching the iOS behaviors, not what the customers want... How hard it is to ask the end user what the need for something as simple as autoplay?” 19. “Kiosk system are going to love this !!!!” 20. “I don't want Chrome creating an algorithm that 'decides' if I want to watch/hear a video. I want a toggle I can set based on MY preferences that applies across the web-verse - with an option to whitelist specific sites if I choose or right-click to play specific videos.” 21. “ bit disappointed how this works. CNN is a big offender mainly because of how they handle playing. It would be nice to account for video playback models such as CNN. Where even if pause the video , it starts autoplay again when in minimizes on scroll. Also being able to control autoplay with a browser setting on a url basis would be nice“ 22. “I don't understand the people who are against a "Never auto-play videos" option and are arguing over this. Can you let me decide what I want please?! There are no arguments you can come up with that will make me change my mind. I'll put it back on if it really is more trouble than anything: how hard is that? “ Many many many more comments can be read here: https://developers.google.com/web/updates/2017/09/autoplay-policy-changes Now, we have plenty of users that want this. Can we reconsider a setting or fix it so the flag is effective??
Showing comments 11 - 110 of 110 Older ›
Sign in to add a comment