Summary: We use autoplay inline muted videos as introduced in iOS10 by Safari browsers. However, when an app is streaming music in the background and we start the video (even muted), the playback of the background app is stopped. In a recent blogpost on the Webkit blog (https://webkit.org/blog/6784/new-video-policies-for-ios/), these new features were named as a way to replace the animated GIF format. But for the moment, the user experience is disappointing when it comes to this use case. Many of our users are complaining. Steps to Reproduce: 1. Open any background streaming sound app 2. Play a sound 3. Press home button (sound is still playing in the background) 4. Open Safari and load http://misc.teads.tv/demo/product/breitlingWithLogo.html 5. Scroll until you see the video (it will automatically start) Expected Results: A good user experience would be to stop the playback only if we activate the sound on the video (user initiated). I guess this is why the requirements around autoplay videos are to have the video muted at start and un-muted only after a user action. We would expect that a playing muted video doesn't disrupt with a streaming background app playback as long as the video stays muted. Actual Results: The playback of the streaming sound app is stopped when the muted video starts on Safari. Version: Safari 10.0 (iOS10)
<rdar://problem/29020431>
Hi, Is there any feedback on this issue? It is becoming more and more a blocker on our side and for our publishers. Here is another test page with a simple video tag on which we have the exact same issue: http://misc.teads.tv.s3.amazonaws.com/demo/product/test-webkit/video.html Steps: - Run a sound streaming app - Sound is playing in background - Launch Safari with the link above - Video is started muted and the streaming app is stopped! Thanks for your help
We are aware of the issue and hope to look into it soon.
Thanks Jon, Do you have any precision on a ETA for this issue to be fixed? This is becoming a blocker on our side and many publishers & users are complaining. Is there anything we could do or anyone we could reach out to and get more visibility on the process? Best, Ibrahim
FYI the bug existed also on Chrome Android. It was fixed since : https://bugs.chromium.org/p/chromium/issues/detail?id=638463 It could help since Chrome is using a fork of Webkit ... Jon, any news on the prioritization of this bugfix?
Hi everyone, Is there any update? Thanks, Ibrahim
Hi Ibrahim, There's been some work done in https://bugs.webkit.org/show_bug.cgi?id=166347, but there's still more to do. I'll keep you updated here.
Created attachment 299829 [details] Patch
Comment on attachment 299829 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=299829&action=review > Source/WebCore/html/HTMLMediaElement.cpp:6851 > + if (m_isPlayingToWirelessTarget) > + return true; This is obvious, so it is probably worth adding a comment to make sure this isn't accidentally changed in the future. > Tools/TestWebKitAPI/Tests/WebKit/ios/video-with-muted-audio-and-webaudio.html:11 > + function go() { > + var audioContext = new webkitAudioContext(); > + audioContext.resume(); > + > + var video = document.getElementsByTagName('video')[0]; > + video.play().then(playing).catch(notPlaying); > + } Nit: funky indentation.
Created attachment 299834 [details] Patch for landing
Created attachment 299854 [details] Patch for landing
Created attachment 299858 [details] Patch for landing
Comment on attachment 299858 [details] Patch for landing Clearing flags on attachment: 299858 Committed r211240: <http://trac.webkit.org/changeset/211240>
Hi, Do you have an idea of when this fix is going to be released? Which iOS version will have it included? Best, Ibrahim
(In reply to comment #14) > Do you have an idea of when this fix is going to be released? Which iOS > version will have it included? We don't discuss release schedules.
Thanks Jon, Is there a way to get notified when the fix is going to be deployed? It is kind of difficult for us to communicate with our clients if we don't have more information about the fix deploy. They are using our technology which is affected by this bug. We appreciate the communication and the work done here. Ibrahim
Not sure why this is still in "new". Moving to "resolved". The fix is in iOS 11. That said we're getting reports that this is still happening. If that is still the case, please follow b177920.
Hi guys, It looks like there was a regression on this bug. It reappeared with iOS11. It was fixed in one of the iOS 10.x versions. But now we have the exact same issue with iOS11. Thanks, Ibrahim
Moving back to resolved. We're tracking additional fixed in 177920.