New issue
Advanced search Search tips

Issue 609982 link

Starred by 2 users
Status: WontFix
Owner:
liber...@chromium.org
Closed: May 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

CL flag --disable-gesture-requirement-for-media-playback not honored

Reported by larrylac...@yahoo.com, May 6 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.36 Safari/537.36

Steps to reproduce the problem:
1. Launch chrome with the flag --disable-gesture-requirement-for-media-playback
2. Look in about:flags it is not disabled
3. Open a help forum page link with Ctrl-select,
  it launches in a new tab without focus.
4. The new tab waits for exposure(focus) to finish loading

Example Help Forum link: https://productforums.google.com/forum/#!topic/chrome/hDb9WeS2uSQ

What is the expected behavior?
CL (CommandLine) flag should be honored, visible in about:flags
Newly opened tabs should finish loading before being brought to the foreground

What went wrong?
The CL flag is not honored
New tabs created with Ctrl-select link are created without receiving focus (OK), but do not finish loading until brought to foreground (bug)

Did this work before? N/A 

Chrome version: 51.0.2704.36  Channel: beta
OS Version: 6.3
Flash Version: Shockwave Flash 21.0 r0

Disabling the flag from about:flags works:
The flag is observed as disabled in about:flags and on the CL status (in about:version)
Pages finish loading before being brought to foreground.

I think the CL arg used to work (m49?), but I'm not sure.
I've had problems with forum tabs waiting to paint which is why I added the CL flag several months ago.

I've attached screen shots of
-Windows shortcut with the CL flag
-CL status from about:version (pre)
-about:flags (pre)
-CL status from about:version (post disable from about:flags)
-about:flags (post after disable)
GestureReqShortcut.png
21.2 KB View Download
GestureReqCLpre.png
89.1 KB View Download
GestureReqFlagPre.png
86.2 KB View Download
GestureReqCLpost.png
88.6 KB View Download
GestureReqFlagPost.png
85.5 KB View Download

Comment 1 by larrylac...@yahoo.com, May 6 2016 

And..

I test with several versions of Chrome.  Most recently I had been using 47.0.2564.73, which does not have the --disable-gesture-req... flag.
Then came back to the current beta 51.0.2704.36, started it from the shortcut with the CL flag,  observed the pages weren't painting in the background
and started digging.

This is why in the first (pre) screenshots the flag is off internally.

Comment 2 by kavvaru@chromium.org, May 10 2016

Components: Internals>Media
Labels: M-52 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on windows 7, Linux Ubuntu 14.04 using chrome version 50.0.2661.94 and canary 52.0.2729.4.The flag "--disable-gesture-requirement-for-media-playback" is not disabled in chrome://flags when launched chrome from command line.

This is non regression issue as the issue seen from M47 builds.This flags is introduced in M47.
Marking it as Untriaged to get more inputs from dev team.

Thanks,

Comment 3 by yini...@chromium.org, May 11 2016

Components: -Internals>Media Internals>Media>UI
Owner: liber...@chromium.org
Status: Assigned (was: Untriaged)

Comment 4 by liber...@chromium.org, May 12 2016 

at first, i suspected that some instance of the flag was accidentally moved behind an #ifdef ANDROID somewhere, but that doesn't seem to be the case.

there's a short-cut around the flag if we're pre-rendering (https://code.google.com/p/chromium/codesearch#chromium/src/chrome/renderer/chrome_content_renderer_client.cc&l=619), that might have something to do with it.

i'll take a look.
Project Member

Comment 5 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 6 by sheriffbot@chromium.org, Jul 11 2016

Labels: -M-53 MovedFrom-53
This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by mlamouri@chromium.org, May 18 2017

Status: WontFix (was: Assigned)
WontFix (Obsolete) as this has changed somewhat (flag name, underlying code, etc.).
►

Sign in to add a comment