Test with the ' bunny' video if you need to. Even if a video doesn't actually HAVE sound it must be muted.The other important things to realize are: You will need to uncomment the line // video.muted = true to get it to work properly. I ran into this in Angular and spent way too much time assuming it was related to the fact I was using a template, or something Angular related. when someone scrolls down past a muted video and you want it to play) then the video must be muted first. If you try to execute ay() programmatically (eg.Therefore if a dynamic video is added to the page you must explicitly set video.muted = true after it is added to the DOM (or right before you play it). If a video with no sound is played programmatically it must be muted first.This also applies to 'autoplay muted' videos. The 'muted' HTML attribute only takes effect when the video is present in the HTML at initial load.Top frames can delegate autoplay permission to their iframes to allow autoplay with sound.On mobile, the user has added the site to his or her home screen.On the desktop, the user's Media Engagement Index threshold has been crossed, meaning the user has previously played video with.User has interacted with the domain (click, tap, etc.).Google's blog entry on autoplay/mute is only a year old, and provides the following insight: This I believe is a bug in Chrome, not occurring for me in Safari - but it looks like we're stuck with it for now.
I think what happens is that the browser makes certain decisions on page load, and for some super odd reason, a video later to the page added will NOT mute even if it has muted property. And since muted doesn't work then muted autoplay won't work either.
Just trying to bring this question up to date and hopefully reduce the number of people wasting a whole day on it (like I just did).Īs far as I can tell (especially since this question is so old) that muted has never worked when the video is dynamically added to the page. There is no real new information in this answer.
0 kommentar(er)
