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

Issue 881409 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 19
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Even though autoplay is disabled, all videos start playing when Chrome is restarted

Reported by flaj...@gmail.com, Sep 6

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Example URL:
YouTube, but any video site exhibits the same behavior

Steps to reproduce the problem:
1. chrome://flags, Autoplay Policy set to "Document user activation is required"
2. Pull up 3 or 4 YouTube videos on seperate windows (not tabs) and start each playing and then pause them
3. killall chrome
4. Restart chrome
5. See that all videos begin playing

What is the expected behavior?
No videos should play until user clicks play on them. Does it really make sense 5 or 10 videos begin playing all at once, especially with the chrome://flag autoplay policy set to user must activate???

What went wrong?
All videos begin playing upon relaunching Chrome

Did this work before? N/A 

Is it a problem with Flash or HTML5? N/A

Does this work in other browsers? N/A

Chrome version: 68.0.3440.106  Channel: stable
OS Version: Kubuntu 18.04 / KDE
Flash Version: 

Contents of chrome://gpu: 

Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Hardware Protected Video Decode: Hardware accelerated
Rasterization: Hardware accelerated
Skia Deferred Display List: Disabled

This behavior used to work properly and correctly with earlier versions of chrome.


 
Cc: gab@chromium.org
Can  you try on Chrome Dev, I believe gab@ just fixed the foreground/background status for these types of windows so they shouldn't start now.
Labels: Needs-Triage-M68
Cc: krajshree@chromium.org
Labels: Needs-Feedback Triaged-ET
As per comment #1, adding label Needs-Feedback.

Cc: -gab@chromium.org
I fixed process foreground/background priority; I don't think it would have affected autoplay (if anything more things were foreground priority before -- the bug I fixed had been around for years to various degrees).
Status: WontFix (was: Unconfirmed)
Closing as Won't Fix(Not Repro) due to no response from reporter. 

Sign in to add a comment