New issue
Advanced search Search tips

Issue 832091 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 828963
Owner: ----
Closed: Apr 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Click on anchor with blob URL in extension context not triggering download

Reported by tho...@mailvelope.com, Apr 12 2018

Issue description

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

Steps to reproduce the problem:
1. Download the test zip, unzip it, and install it in Chrome.
2. Click on the browserAction button and click on the one entry in the menu
3. A new tab opens, showing an iframe, click on the link "Download blob"

What is the expected behavior?
A file download should be triggered.

What went wrong?
No download, no error in the console. The only thing that works is a right-click on the link and "Save link as..." will download the file as expected.

Did this work before? Yes 64

Does this work in other browsers? Yes

Chrome version: 65.0.3325.181  Channel: stable
OS Version: OS X 10.13.4
Flash Version: 

Reported this issue also here: https://bugs.chromium.org/p/chromium/issues/detail?id=761341#c29
I would like to select component Platform>Extensions for this bug, but the selection in the bug report form only shows Blink components.
 
test-blob-download.zip
4.3 KB Download

Comment 1 by woxxom@gmail.com, Apr 12 2018

Fixed in 02c5490ce8a43336110d8210747d88202352e009
"Use old download path for same-origin downloads"
Landed in 67.0.3390.0
Merged to 66.0.3359.100
Labels: Needs-Bisect Needs-Triage-M65
Components: Platform>Extensions
Labels: -Needs-Bisect Triaged-ET
Mergedinto: 828963
Status: Duplicate (was: Unconfirmed)
Thanks for filing the issue!

Able to reproduce the issue on chrome reported version 65.0.3325.181 and previous beta 66.0.3359.81 but the same issue is not seen on latest beta 66.0.3359.106. As per commit provided in comment#1, duplicating the original issue:  832091  into the issue:  828963  which was interlinked in the commit, hence merging it to issue:  832091 .

Thanks! 

Sign in to add a comment