[Bug] PDF Sometimes Not Imported via Drag and Drop
Report ID: 78542986
System: MacOS
If you drag and drop a PDF, quickly delete it, and then try to import it again nothing happens and an error message is printed to the console.
Steps to Reproduce:
1. Drag a PDF to the window to import it.
2. Delete the PDF via the menu option to move to trash
3. Try to import the same PDF
The error message is:
TypeError: event.dataTransfer is null itemTree.js:2150:11
Error: An error was thrown inside one of your components, but React doesn't know what it was. This is likely due to browser flakiness. React does its best to preserve the "Pause on exceptions" behavior of the DevTools, which requires some DEV-mode only tricks. It's possible that these don't work in your browser. Try triggering the error in production mode, or switching to a modern browser. If you suspect that this is actually an issue with React, please file an issue. react-dom.js:4000:21
All extensions are deleted from Zotero. I tried turning off the rename file feature to see if that was the issue but it still persisted.
System: MacOS
If you drag and drop a PDF, quickly delete it, and then try to import it again nothing happens and an error message is printed to the console.
Steps to Reproduce:
1. Drag a PDF to the window to import it.
2. Delete the PDF via the menu option to move to trash
3. Try to import the same PDF
The error message is:
TypeError: event.dataTransfer is null itemTree.js:2150:11
Error: An error was thrown inside one of your components, but React doesn't know what it was. This is likely due to browser flakiness. React does its best to preserve the "Pause on exceptions" behavior of the DevTools, which requires some DEV-mode only tricks. It's possible that these don't work in your browser. Try triggering the error in production mode, or switching to a modern browser. If you suspect that this is actually an issue with React, please file an issue. react-dom.js:4000:21
All extensions are deleted from Zotero. I tried turning off the rename file feature to see if that was the issue but it still persisted.