Bug 211234 - [iOS] Revoking an object URL immediately after triggering download breaks file download
Summary: [iOS] Revoking an object URL immediately after triggering download breaks fil...
Status: RESOLVED DUPLICATE of bug 212279
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Misc. (show other bugs)
Version: Safari 13
Hardware: iPhone / iPad iOS 13
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2020-04-30 07:38 PDT by Henning Stummer
Modified: 2021-01-20 22:49 PST (History)
6 users (show)

See Also:


Attachments
File with a test download (867 bytes, text/html)
2020-04-30 07:38 PDT, Henning Stummer
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Henning Stummer 2020-04-30 07:38:13 PDT
Created attachment 398053 [details]
File with a test download

Load the attached file in Safari on iOS:

When you click on "Download" you get an error page with the following text:
"The operation couldn't be completed. (WebkitBlobResource error 1.)"

When you add a timeout before revoking the objectURL, the download start, but the "download" attribute is ignored. The file will get the filename "unknown" instead.
Comment 1 Radar WebKit Bug Importer 2020-05-01 10:37:22 PDT
<rdar://problem/62735862>
Comment 2 Chris Dumez 2020-05-22 12:25:40 PDT
(In reply to Henning Stummer from comment #0)
> Created attachment 398053 [details]
> File with a test download
> 
> Load the attached file in Safari on iOS:
> 
> When you click on "Download" you get an error page with the following text:
> "The operation couldn't be completed. (WebkitBlobResource error 1.)"

Bug 185531 was the fix for this and it seems to be working fine on macOS. However, it indeed does not seem to work as expected on iPadOS with your example for some reason.

> When you add a timeout before revoking the objectURL, the download start,
> but the "download" attribute is ignored. The file will get the filename
> "unknown" instead.

I was not able to reproduce this but I am on a beta build. It may have been fixed or it is flaky because of 100ms timer.
Comment 3 Chris Dumez 2020-05-22 14:24:13 PDT
I have verified that fixing Bug 212279 fixes this too.

*** This bug has been marked as a duplicate of bug 212279 ***