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

Issue 798360 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : YouTube video does not autoplay when video is opened in a new tab.

Reported by avsha...@etouch.net, Jan 2 2018

Issue description

Chrome Version : 65.0.3309.0 (Official Build) 7f5c6c7cbfeb43b7cb082829d8b05a0197d9b151-refs/heads/master@{#526409} 32/64-bit
OS : Mac(10.12.6, 10.13.1, 10.13.3), Windows(7,8,10), Linux(14.04 LTS)

What steps will reproduce the problem?
1. Launch chrome, open NTP and navigate to www.youtube.com
2. Now Right click (or Middle click) on any video, select 'Open link in new tab' option and observe the video.

Actual Result : YouTube video does not autoplay when video is opened in a new tab.

Expected Result : Video should start to autoplay when video is opened in a new tab.

This is a regression issue broken in ‘M-65’ and using the per-revision bisect providing the bisect results,
Good build : 65.0.3299.0 (Revision : 524907)
Bad build : 65.0.3300.0 (Revision : 525555)

You are probably looking for a change made after 524986 (known good), but no later than 524987 (first known bad).

CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/64e4aa7223ee1ebef7874515aaf30b7e64c24f50..7b74ab4850b0115a996f0076733bc90fc7f8a273

Suspect : https://chromium.googlesource.com/chromium/src/+/7b74ab4850b0115a996f0076733bc90fc7f8a273

@mlamouri : Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Note : This is not observed on Firefox, Safari browser.
 
Actual_Video_Autoplay.mov
8.3 MB Download
Expected_Video_Autoplay.mov
10.5 MB Download
Status: WontFix (was: Assigned)
Thank you for the report. This is totally related to my change and is because of the autoplay restrictions that are now applying on Chrome trunk and Chrome Dev. This is however intentional.
Labels: ET-MUM-Reported

Sign in to add a comment