Bug 263608
Summary: | TXT and XML Files open in tab on iOS Safari instead of downloading | ||
---|---|---|---|
Product: | WebKit | Reporter: | Celeste Glavin <cglavin> |
Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW | ||
Severity: | Normal | CC: | aron, bugmail, ddkilzer, laszlo.alt, ppoollllxx, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | Safari 16 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=167341 |
Celeste Glavin
Steps to reproduce:
- define an anchor element with the download attribute and a url to download either a TXT or XMl file
- fire the click event on iOS Safari (Current version is 16.6.1)
Expected:
- Download starts
Actual:
- file is opened in the current tab
Example of code:
const downloadExportUrl = (url) => {
const a = document.createElement('a');
a.href = url;
a.download = '';
a.click();
};
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/117435170>
pollx
Same issue when trying to download a pdf file in the form of Blob:
const pdfBlob = await pdfBinaryRes.blob()
const blobUrl = window.URL.createObjectURL(pdfBlob)
const link = document.createElement('a')
link.href = blobUrl
link.download = filename
link.click()
Laszlo
I get the same result with pictures as well.
Laszlo
I get the same result with pictures as well.
aron
I'm having the same problem with plain old html. I have also confirmed that the server serves the file with the attachment content disposition, and it works on desktop safari but not ios.
The link I have is to a different sub-domain incase that helps.
Laszlo
(In reply to aron from comment #5)
> I'm having the same problem with plain old html. I have also confirmed that
> the server serves the file with the attachment content disposition, and it
> works on desktop safari but not ios.
>
> The link I have is to a different sub-domain incase that helps.
I had another bug somewhere on webkit and they responded that the issue lies with Safari and the Safari was notified of the issue. It will be tracked internally in the Safari team so we will not know the status of it going forward.