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

Issue 777515 link

Starred by 6 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Impossible to playback swf files from a direct link on Chrome 62

Reported by davidon...@gmail.com, Oct 23 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36

Example URL:
http://samples.mplayerhq.hu/SWF/test.swf

Steps to reproduce the problem:
1. Navigate to the swf url
2. Chrome attempts to download the file instead of asking for the user to play it back.

What is the expected behavior?
When navigating to a direct link to a swf file, Chrome should prompt the user for authorization to run it (or run it if the domain was whitelisted on chrome://settings/content/flash ).

What went wrong?
It's impossible to play back swfs if opened via a direct link.

Did this work before? Yes 61

Chrome version: 62.0.3202.62  Channel: stable
OS Version: OS X 10.12.6
Flash Version:
 

Comment 1 by asha...@msad51.org, Oct 23 2017

I'm noticing this on both Mac and ChromeOS.
Labels: Needs-Bisect Needs-Triage-M62 OS-Chrome

Comment 3 by mmenke@chromium.org, Oct 23 2017

Components: -Internals>Network UI>Browser>Downloads UI>Browser>Navigation
Don't think this is a network issue, since we successfully download the file.  Maybe a change with PlzNavigate or downloads?

Comment 4 by mmenke@chromium.org, Oct 23 2017

Components: Internals>Plugins>Flash
Actually, could also be a deliberate deprecation.

Comment 5 by dah...@chromium.org, Oct 26 2017

Cc: clamy@chromium.org johnpallett@chromium.org ericde@chromium.org
clamy@ do you think this could be a PlzNavigate issue?

johnpallett@, ericde@, is this the expected behavior for flash deprecation?
Cc: groby@chromium.org lafo...@chromium.org
+laforge +groby

Comment 7 by laforge@google.com, Oct 26 2017

Status: WontFix (was: Unconfirmed)
Correct, per comment #4, this is a deliberate change as of Chrome 55/56.  We actively block Flash Player by default, when SWF files are loaded directly there is not UI surface to add activation control to (i.e., normally those would be rendered in the web content area).  Best suggestion would be to iframe in swf content.

Sign in to add a comment