Skip to content
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

Chrome's FileSystem API has a bug reading files from dropped folders or input dialog's selected folder #301

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

vsta
Copy link

@vsta vsta commented Jul 6, 2020

Chrome 83.0.4103.61, Windows 10.0.18362 Chrome's FileSystem API has a bug that files from dropped folders or files from input dialog's selected folder, with read errors (has absolute paths which exceed 260 chars) will have zero file size.
When dropped folder has any file with absolute paths which exceeds 260 chars, upload should report read errors.
When input dialog is used to select folder, files with absolute paths which exceeds 260 chars, will be uploaded with zero length. These files should not be uploaded, it should report read errors.

Firefox 76.0.1, Windows 10.0.18362 doesn't have this bug, but it will not upload files with absolute path which exceeds 260 chars.

Edge 44.18362.449.0, Windows 10.0.18362 uploads all files regardless of the absolute path length.

… bug that files from dropped folders or files from input dialog's selected folder, with read errors (has absolute paths which exceed 260 chars) will have zero file size.

When dropped folder has any file with absolute paths which exceeds 260 chars, upload should report read errors.
When input dialog is used to select folder, files with absolute paths which exceeds 260 chars, will be uploaded with zero length. These files should not be uploaded, it should report read errors.
@@ -230,55 +230,109 @@
*/
webkitReadDataTransfer: function (event) {
var $ = this;
var queue = event.dataTransfer.items.length;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's unlikely such a huge diff (+149 −52) could be efficiently reviewed. Could you provide a minimum testcase (in the test folder) and a less intrusive bugfix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants