Reputation: 913
As of version 66 of Google Chrome onwards it will no longer automatically start playback of audio and video files when the playback volume is not muted.
This change was made to prevent autoplay on ad videos and other annoying web page elements. However, this has negative consequences for a number of perfectly valid applications of the autoplay feature, for instance in signage applications.
The new default behaviour of not auto playing a video with sound can be overridden at the startup of the Google Chrome browser with the command line options
--autoplay-policy=no-user-gesture-required
or
--no-user-gesture-required
The new default autoplay behaviour is also present in the Chrome browser on ChromeOS (currently in the beta channel). For Kiosk-apps running on ChromeOS there are no command line options, only configuration using the Manifest.json file.
Currently there is no option in the documentation of the Manifest.json format that allows changing the autoplay policy.
Is there any way to change the new Chrome default autoplay policy in Kiosk apps to allow autoplay of videos in an app on ChromeOS?
Upvotes: 23
Views: 40404
Reputation: 51
For a kiosk, I added this site to chrome://settings/content/sound
file:///*
This allowed videos with autoplay to have sound for local files.
Upvotes: 5
Reputation: 176
This function is often useful on kiosks, where you want to autoplay sound from one specified site. In that case, you can just to to:
And enable autoplay for particular website. It should override its default behaviour and play the sound immediately after displaying site.
Upvotes: 12
Reputation: 4870
It turns out that the end user will have to enable automatic video playback manually, by:
chrome://flags/#autoplay-policy
From now on autoplay works again in webview components used in your app.
See this comment thread about this topic by Google.
Upvotes: 17