NEW 277884
File inputs in Safari PWA can no longer be triggered
https://bugs.webkit.org/show_bug.cgi?id=277884
Summary File inputs in Safari PWA can no longer be triggered
Tanishq
Reported 2024-08-09 14:42:46 PDT
- Click on an element that programmatically triggers a `.click` on a hidden file input using Javascript Expected: - Opens the file picker Seen: - Nothing happens Here is a minimal reproduction: https://stackblitz.com/edit/vitejs-vite-5rwx31?file=index.html Note you must download the project first, run it locally, and then install as a PWA. Downloading the preview link as a PWA does not work. Safari: Version 17.6 (19618.3.11.11.5) MacOS: 14.6.1 (23G93)
Attachments
Radar WebKit Bug Importer
Comment 1 2024-08-16 14:43:13 PDT
Tanishq
Comment 2 2024-08-23 10:12:14 PDT
After some debugging, I noticed that it's not only programmatic triggering. You can no longer activate file inputs on Safari on the latest PWA (by clicking or programmatically). I am personally able to repro this and we are getting user reports of this as well. This seems like a high priority bug. Is there anything I can do to expedite a fix for this?
Aditya Keerthi
Comment 3 2024-08-23 10:36:18 PDT
Can you elaborate what you mean by download the project first, run it locally, and then install as a PWA? I added MDN as a Home Screen Web App, visited https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/file, and was able to open the file input successfully.
Tanishq
Comment 4 2024-08-23 10:51:49 PDT
@Aditya, I performed the exact same action (install MDN to home page), and was not able to open the input. Clicking on the file input in the examples did not open the file picker for me. We can use that page as the repro, my repro steps were more complex. Are you certain you are on the Safari and MacOS versions I listed?
Aditya Keerthi
Comment 5 2024-08-23 11:04:33 PDT
I was indeed using a different configuration. I can reproduce the issue with your configuration. However, I believe this should be fixed in the latest macOS Sequoia beta.
Note You need to log in before you can comment on or make changes to this bug.