New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 835842 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 0
Type: Bug-Regression



Sign in to add a comment

Autoplay not enabled when MEI is high

Project Member Reported by johnpallett@chromium.org, Apr 23 2018

Issue description

Chrome Version: 66.0.3359.117 (Stable, Official Build, 64-bit)
OS: Win10

What steps will reproduce the problem?

TL;DR if you set MEI high for arabic.cnn.com the following site does not autoplay: https://arabic.cnn.com/sites/default/files/static/cnn/autoplay/chrome/autoplay.html

Detailed steps to repro:

(1) Enable autoplay policy (chrome://flags#autoplay-policy :: set to "Document user activation")
(2) If necessary, clear browsing data so that MEI for arabic.cnn.com is reset
(3) Set MEI for arabic.cnn.com to allow autoplay by repeating the following steps (3a)-(3d) at least 6 times:
(3a) Confirm that all cnn.com tabs are closed
(3b) Open https://arabic.cnn.com/sites/default/files/static/cnn/autoplay/chrome/autoplay.html
(3c) Play the video for at least 7 sec.
(3d) Close the tab
(4) Now visit the same site - autoplay should work but isn't. Confirm that MEI has enabled autoplay for arabic.cnn.com


What is the expected result?
When MEI is high, site should autoplay

What happens instead?
Autoplay is blocked

Note: I checked Canary 68.0.3403.0 and it doesn't seem to be a problem
 
Cc: prabhu.d...@turner.com
Labels: -Restrict-View-Google
I can reproduce this but if I enable the MediaEngagementBypassAutoplayPolicies feature it is working.

It looks like what has happened here is that the autoplay policy flag was enabled but the feature to enable MEI to bypass autoplay policies was still turned off.

Please can you run chrome with the following command line flags and try again?

--enable-features=MediaEngagementBypassAutoplayPolicies,UnifiedAutoplay
To clarify, the chrome://flags#autoplay-policy only changes the policy but doesn't enable MEI. The roll out of the feature enables a couple of flags, including chrome://flags#autoplay-policy (but not only).
Cc: abdulsyed@chromium.org
Labels: -Type-Bug FoundIn-66 ReleaseBlock-Stable Target-66 OS-Windows Type-Bug-Regression
Labels: -ReleaseBlock-Stable
Status: WontFix (was: Assigned)
Confirmed with Prabhu that the issue goes away when using the correct flags.

Thanks Becca, marking as WontFix

Sign in to add a comment