Edge Doesn't Use download attribute to set filename for blob URI downloading

Fixed Issue #7260192

Details

Author
Michael S.
Created
Apr 19, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Standard affected
a[download

Found in build #
14.14344
Reports
Reported by 12 people

Sign in to watch or report this issue.

Steps to reproduce

The download attribute doesn’t appear to be used when “downloading” a hyperlink containing a blob href.
Test Case: https://jsfiddle.net/08dzeq3e/6/
IE => Doesn’t download at all
Edge => Downloads with filename"E0F5CA16-F4AA-4B18-9A07-BFDD1F0633BD"
Chrome => Downloads with filename “my-download.json”
Firefox => Downloads with filename “my-download.json”

Filename is also not set correctly when using a markup syntax like: http://www.w3schools.com/tags/tryit.asp?filename=tryhtml5_a_download2

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Christian F.”

      Changed Assigned To from “Christian F.” to “Divya G.”

      Changed Steps to Reproduce

      Changed Title from “Edge Doesn't Use download attribute for blob URI downloading” to “Edge Doesn't Use download attribute to set filename for blob URI downloading”

      Changed Status to “Confirmed”

    • This bug is confirmed and will be addressed, however to set expectations, it is not expected to make the summer update due to complexity of the fix.

    • A workaround while this is fixed is to use msSaveOrOpenBlob method. This will trigger an “Open or Save” prompt with the correct name.

      var jsonContent = fileContent;
      var blob = new Blob([jsonContent], { type: “application/json” });
      window.navigator.msSaveOrOpenBlob(blob, fileContent.name + “.json”);

      You’ll need to add your own logic to determine the browser type, etc.

      Hope this helps!

      • JC
    • The fix for this is now in code review.

    • Microsoft Edge Team

      Changed Status from “Confirmed” to “Fixed”

    • Fixed in internal branch and making its way to Insider builds in the next 1-2 weeks.

    • Thank you for your work and notification :D

    • I still see download attribute issue in Version: 11.0.9600.18538. Also, msSaveOrOpenBlob gives download popup but, on click of open/save it always says, This file couldn’t be downloaded with retry button. Somehow the download & msSaveOrOpenBlob works fine in Version 11.0.9600.18537. Can you please clarify me the fix for this issue?

    • IE11 will not receive any feature fix.

    • So, what is the work around then to make it work in IE Version: 11.0.9600.18538.

    • Will the fix solve the issue shown in the w3schools example as well? Where a regular href is used, rather than a blob URI.

    • Hello, what is the status of this bug?

    • These problems (especially the one given in the school logo example) are still being experienced. What is the status of deploying this fix?

    • These problem are still being experienced. The download attribute content is ignored. Also, if the file extension isn’t recognized, Edge changes the file extension (e.g. file.jnk becomes file_jnk.txt). My version of Edge is 41.16299.248.0 which is the most recent but the release date is 09/26/2017 which doesn’t seem like the most recent. There is a lot of complaining on the internet about the download attribute not working, some of it recent. The comment above mine is one example.

    • The download attribute is still not being respected on Microsoft Edge 16.

    • Have you tried Edge 17?

    • I just ran Edge 17 on browserstack and tried another file with a download attribute and the while the problem is nowhere near fixed, it did change the filename.
      Before it would name the file something like this: “E0F5CA16-F4AA-4B18-9A07-BFDD1F0633BD”
      And this time it named it: (1) or (2).
      Which is still incorrect from what the download attribute is set to and the extension is still ignored.

    • Hmm, then Edge 18 would be the first version that fixes this, as I can confirm it correctly names the file.

    You need to sign in to your Microsoft account to add a comment.

    Sign in