-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should .webkitEntries be populated for dialog selections? #15
Comments
Yes, definitely. It is ridiculous that a directory tree can be selected by a Drag&Drop operation but not by the File Picker Dialog. See what kind of problems this is causing: |
Well, this particular spec is trying to document the behavior of browsers, not set a direction. But the spec doesn't make it clear that browsers are weird here... It's called out as: https://wicg.github.io/entries-api/#issue-4cc238bb
Yep - it's not good. Browsers should do better here...
😢 |
Dang almost 5 years no resolution?? |
Right now, Firefox populates an input element's
.webkitEntries
only when files are dragged-and-dropped onto the element, not when the file dialog is clicked and a file manually selected: https://bugzilla.mozilla.org/show_bug.cgi?id=1326031Chrome behavior is similar, but after a file has been dragged-and-dropped, the selection can be changed in the dialog and the change will be reflected in
.webkitEntries
.Both browsers' behavior appears to me to be in violation of the spec, and to present an accessibility issue as drag-and-drop is often cumbersome to use. Am I misreading this?
The text was updated successfully, but these errors were encountered: