Google has exempted its own from this indexing. I have projects on origins which qualify, but still refuse to autoplay and project which do not qualify, but do autoplay.Ī guest session is said to start with a fresh index, but I have never seen this make a difference. You can see your current stats in chrome://media-engagementīut these stats are unreliable. This is very annoying as aborting videos too soon, like you do during development, gets you further away from autoplay. It is said you need to (manually) play at least 7 seconds of video (with audio) After doing that about 20 times Googles Media Engagement Index database will have learned you want to allow autoplay for that site.īut mind you, playing videos shorter might get your site disqualified again. Whether autoplay is allowed is now determined by magic. To my experience somewhere between version 70 and 80 the -autoplay-policy=no-user-gesture-required parameter stopped working. I hope somebody can help with that and maybe have a explanation. 93-0ubuntu0.18.04.1įor testing purposes i used the following simple html (i also tried it without the source tag). We also have (sometimes) a few weired behaviors, sometimes the sound is played but the video not. Unfortunaly this is not the case, i still have to start the video myself. I searched for a way to reenable the autoplay (with sound!), i found the parameter "-autoplay-policy=no-user-gesture-required" which should reenable the autoplay. I could figure out that the autoplay behavior has changed ( ).
Pano2vr player chrome autoplay not working update#
We want to update to the newest version (90), but as soon we update the autoplay don't work as before.
We have a kiosk system (running on ubuntu) which used chromium 65 until now.
0 kommentar(er)
