Hi,
I am building a small application using the ADF framework and it includes the Drag and Drop area component. This works fine when dragging in from the file system but the result varies when dragging an email in from outlook.
The .msg file does correctly get uploaded, but it is 'deleted' from the Outlook client. Ctrl-z does bring it back, but that's not an ideal solution.
The issue appears to be different defaults across the browsers for the .dropEffect setting:
https://developer.mozilla.org/en-US/docs/Web/API/DataTransfer/dropEffect
The default in Chromium/Chrome at the moment in this case is .dropEffect = "move" rather than .dropEffect = "copy".
Does anyone know of a setting/code change that I can make that would allow me to explicitly set this on the ADF component rather than relying on the browser default? In this case I would expect the underlying component to always be set to "copy" rather than "move".
Any help would be appreciated!
Solved! Go to Solution.
It should be part of the 4.0 release. The corresponding changes have been merged before the release.
This has been fixed already and will be available in the next release of ADF (4.0)
Awesome! Is there any option for older versions? Am not sure when I can upgrade to ADF 4 and have an existing customer complaining that their email is going missing.
Also, can I get an idea of when the 4.0 release will be?
Hi,
I tried the 3.10-beta3 that has this fix in the directive. But it didn't seem to help for me when using the adf-upload-drag-area control. Is the directive used by this component under the covers?
I'm working against a beta I know, but just trying to work out if I need to build a custom div that uses the directive to get this fix.
Cheers,
Matt
Thank you for the feedback. I have identified an issue and working on a fix
Can I assume the fix will not be in 4.0 as I was just notified that was already released. So perhaps a 4.1 beta? Just need to be able to give some info to my PM.
It should be part of the 4.0 release. The corresponding changes have been merged before the release.
OK, awesome, just upgrading now... will let you know how it goes. Appreciate the assistance.
Just tested and it does appear to be working in 4.0 for my case! Thanks!
Discussions, help and advice about the Alfresco Development Framework.
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.