Reputation: 4879
In Google Chrome 66, autoplay policy changed.
You can read about it here:
https://developers.google.com/web/updates/2017/09/autoplay-policy-changes
As a developer, I need to develop workarounds.
Of course, the first step to developing for this scenario is being able to reliably reproduce the scenario where:
Here's my issue.
Os X, Chrome 67.0.3396.99
Steps to Reproduce:
This means:
a) Visit chrome://flags/#autoplay-policy
and change the behavior to Document user activation is required
and restart Chrome.
b) Run Chrome using: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --disable-features=PreloadMediaEngagementData,AutoplayIgnoreWebAudio,MediaEngagementBypassAutoplayPolicies
Expected Result:
Autoplay doesn't engage.
Actual Result:
It does.
Thanks in advance.
Upvotes: 1
Views: 2475
Reputation: 4879
It turns out that
Step (a) appears to be unnecessary.
When running step (b) make sure that you close Chrome entirely first. If you get the message "Created new window in existing browser session", you are in trouble.
To reiterate:
Steps To Reproduce:
1) Quit Chrome entirely.
2) Run Chrome using: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --disable-features=PreloadMediaEngagementData,AutoplayIgnoreWebAudio,MediaEngagementBypassAutoplayPolicies
3) Visit YouTube.com
Result:
Video starts paused.
I've found, additionally, that my videos will still autoplay unless I click the address bar and click "enter", rather than refreshing the page.
Upvotes: 1