263608 2023-10-24 13:12:24 -0700 TXT and XML Files open in tab on iOS Safari instead of downloading 2024-09-09 13:58:53 -0700 1 1 1 Unclassified WebKit DOM Safari 16 Unspecified Unspecified NEW https://bugs.webkit.org/show_bug.cgi?id=167341 InRadar P2 Normal --- 1 cglavin webkit-unassigned aron bugmail ddkilzer laszlo.alt ppoollllxx webkit-bug-importer oldest_to_newest 1987209 0 cglavin 2023-10-24 13:12:24 -0700 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(); }; 1987231 1 webkit-bug-importer 2023-10-24 14:10:54 -0700 <rdar://problem/117435170> 2004421 2 ppoollllxx 2024-01-11 06:29:40 -0800 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() 2040464 3 laszlo.alt 2024-06-07 19:03:23 -0700 I get the same result with pictures as well. 2040465 4 laszlo.alt 2024-06-07 19:03:37 -0700 I get the same result with pictures as well. 2058711 5 aron 2024-09-09 13:35:06 -0700 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. 2058714 6 laszlo.alt 2024-09-09 13:58:53 -0700 (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.