Closed munkyxtc closed 10 years ago
I was playing a bit more and found that its actually a cache issue in IE. Each drop after a subsequent file explore is using the selected file from the file explorer. I am assuming this is an IE specific caching issue.
. I am assuming this is an IE specific caching issue.
True, and besides drag & drop for IE 6-7 and maybe 8 (I don't remember now) as far as I have tested does fire ondrop even but you cannot transmit the data, there's no source and no method for that like sendAsBinary
or similar that XHR has in modern implementations. For this reason I have disabled ondrop handling in IE.
I believe the issue I am experiencing is related to the April change log which reads:
"dropping file in IE now doesn’t trigger upload since IE doesn’t fill with the dropped file name"
I want to confirm that this behavior is actually the result of this change. What I am experiencing is as follows:
I am trying to create a simple proof of concept using FileDrop and I found an issue in IE8 which I can easily reproduce using the demo page.
When the page is first loaded in IE dragging a file to the drop area does not trigger an http request as I would expect. In FF & Chrome it does send the request. If you click in the drop area to be shown the file selection dialog choose a file and upload a request is sent as expected.
After this action you can now successfully drag and drop files into the drop area in IE; but not until you manually choose a file from the dialog first.
I don't see any errors occurring in developer tools. Setting iframe forced = true does not seem to resolve the behavior.