Bug 277884
Summary: | File inputs in Safari PWA can no longer be triggered | ||
---|---|---|---|
Product: | WebKit | Reporter: | Tanishq <tanishq> |
Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW | ||
Severity: | Major | CC: | akeerthi, ap, bfulgham, cdumez, karlcow, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | Safari 17 | ||
Hardware: | Mac (Apple Silicon) | ||
OS: | macOS 14 |
Tanishq
- 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 | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/134086471>
Tanishq
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
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
@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
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.