Bug 211234

Summary: [iOS] Revoking an object URL immediately after triggering download breaks file download
Product: WebKit Reporter: Henning Stummer <henning>
Component: WebKit Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: Andy_Schmidt, cdumez, david_quesada, felek.000, henning, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Safari 13   
Hardware: iPhone / iPad   
OS: iOS 13   
See Also: https://bugs.webkit.org/show_bug.cgi?id=185531
Attachments:
Description Flags
File with a test download none

Henning Stummer
Reported 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.
Attachments
File with a test download (867 bytes, text/html)
2020-04-30 07:38 PDT, Henning Stummer 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2020-05-01 10:37:22 PDT
<rdar://problem/62735862>
Chris Dumez
Comment 2 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.
Chris Dumez
Comment 3 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 ***
Note You need to log in before you can comment on or make changes to this bug.