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

Issue 700274 link

Starred by 7 users

Issue metadata

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



Sign in to add a comment

Local State file causing Chrome to download website links instead of opening.

Reported by halokidd...@hotmail.com, Mar 10 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0

Steps to reproduce the problem:
1. Open Chrome
2. Go to http://playhousefriends.com/
3. Click Video Chat and watch it try to download instead of opening.

What is the expected behavior?
The link should open to a flash based web chat.

What went wrong?
The link instead chooses to download the flash as a .swf instead of opening in the browser.

Did this work before? N/A 

Chrome version: 57.0.2987.98 (Official Build) (64-bit)  Channel: n/a
OS Version: 8.1
Flash Version: Shockwave Flash 24.0 r0

This used to work obviously because this only started to happen recently. Deleting the Local State file while Chrome is fully closed resolves this issue. I've had this "fix" work for several people.

 

Comment 1 by gov...@chromium.org, Mar 10 2017

Cc: pbomm...@chromium.org ranjitkan@chromium.org lafo...@chromium.org
Cc: gov...@chromium.org brajkumar@chromium.org
Components: Internals>Plugins>Flash
Labels: -Type-Bug -Pri-2 hasbisect-per-revision M-59 OS-Linux OS-Mac Pri-1 Type-Bug-Regression
Owner: japhet@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce on Windows-10, Ubuntu 14.04 and Mac OS 10.12.3 using chrome stable M57-57.0.2987.98.

Bisect Information:
=====================
Good build: 54.0.2836.0
Bad Build : 54.0.2838.0

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/3bd5a3238b915071532c92c9d6f63cc844a66be9..8489f1bf78c2c6f296e0df6c529751d29e8a0188

From the above change log suspecting below change
Review URL: https://codereview.chromium.org/2211283004

japhet@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Note: While testing this issue observed two bad behaviors while opening the page, either it downloads .swf file or it opens a blank page with out downloading the .swf file, so considering both as bad behaviors and providing the bisect info.

Thanks! 

Comment 3 by laforge@google.com, Mar 10 2017

Cc: ericde@chromium.org groby@chromium.org tommycli@chromium.org
Owner: tommycli@chromium.org
Not sure why local state would matter in this case, having never visited that site before it immediately prompts to download.

My suspicion is that this is working as intended.  With the launch of HTML5 by Default we no longer permit SWF files from being launched directly (because they don't afford any way for the user to interact w/ the content before running it).  The fix for this would be on the developer's end, by putting an iframe around the .swf file, versus attempting to load it directly.
Not sure if my comment went through, delete this if it did.
Is this something Chrome has to fix or Shivtr?

Is there a fix for the end user aside from deleting the local state file? If we don't the website never opens properly for us. 
I should add there are people telling me that Firefox retains this issue until the Local State file has been deleted, not sure if that helps or not.

Status: WontFix (was: Assigned)
I have confirmed the issue. I'm guessing deleting Local State works (sometimes) because it probably resets the user's randomly-assigned Field trial config.

There is a problem if the HTML5 By Default feature is on. (Flash is hidden)

The site triggers a download of the the SWF file if Flash is not detected. That's something the site needs to fix. Chrome is working as intended.

For reference, Firefox also triggers a download of the SWF file.

Thanks!

Tommy
 Issue 702472  has been merged into this issue.
Cc: ligim...@chromium.org
 Issue 761679  has been merged into this issue.
FYI
 Issue 761679  is a dup of  issue 767342  per the OP.
761679 was merged into this  issue 700274  but 767342 was not.

 Issue 767322  is locked.  Someone else will need to leave a forward trail there.

Sign in to add a comment