Issue metadata
Sign in to add a comment
|
Bypass of Autoplay Policy Changes
Reported by
polskafi...@gmail.com,
Aug 13
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Example URL: https://lunaris.play.ai/poc.html Steps to reproduce the problem: 1. Create a <video> 2. Use snippet: function init(){ setTimeout(function(){ document.getElementById("vid").muted = false; document.getElementById("vid").play(); }, 50); } 3. Bypass muted autoplay video restriction What is the expected behavior? Video should stay muted, because user did not interact What went wrong? By delaying script execution, we can bypass Autoplay Policy Changes and still autoplay video with sound. Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 68.0.3440.106 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 30.0 r0
,
Aug 13
Thanks for the report! It seems that I can reproduce this, indeed.
,
Aug 13
After a bit of testing, it appears you can also do this in Android's Chrome, but you need to increase function timeout a bit (about 1000)
,
Aug 13
,
Aug 13
A better solution might be a control in chrome://settings/content that enables the user to choose whether or not to allow video to play - period. There have been instances when I've attempted to read an article, and there were two or more third party video advertisements that auto-played [thankfully muted] - consuming so many resources that even scrolling down the page was painfully slow.
,
Aug 13
Unfortunately, blocking muted videos is not the right solution. This used to be the common policy on mobile for Chrome and Safari and websites simply kept using animated images or even sometimes dececoded videos in javascript. Both are significantly worse for resources than a video playing muted. Realistically, the only thing the browser can control is whether sound is going out.
,
Aug 13
I cannot reproduce this on Linux with 68.0.3440.112 or 70.0.3518.0 with both dev and release builds. Also, did you have the devtools open when you were able to do this? There is a bug where having devtools open may count as a user gesture. @mlamouri - which version could you reproduce it on?
,
Aug 13
I'm running with 69.0.3497.12 (Dev) on Linux. I have a pending update which I guess might move me to 70.*. I can try on my laptop later which is more up to date.
,
Aug 13
Just tested on 70.0.3514.0 (Dev) and I can't repro. Same on 69.0.3497.32 (Beta) and 68.0.3440.106 (Stable). (・_・ヾ
,
Aug 13
polskafi...@gmail.com - can you reproduce this on dev or beta?
,
Aug 13
,
Aug 14
It stopped working for some unknown reason, but I increased the timeout to 1000 and it works again, but not always: https://lunaris.play.ai/poc2.html
,
Aug 15
I still cannot repro this on Linux or Mac.
,
Aug 16
I still cannot reproduce this on 68.0.3440.106 (Windows 64 bit). Please can you go to chrome://version and copy and paste your "Variations" section here?
,
Aug 17
,
Aug 20
,
Sep 27
The NextAction date has arrived: 2018-09-27
,
Oct 1
We still cannot reproduce this and the issue has been waiting feedback for 30 days so closing. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Aug 13