Downloads dragged and dropped from Firefox download window into Outlook e-mail show as file location text.
I have a user who normally can drag files from Firefox's Download window into an e-mail in Outlook and it creates an attachment of that file in the e-mail. However, lately, the dragged .pdf or whatever file only shows up as a text file location like:
\\file:%Downloads%\randomfile.pdf
It's not a link either, it's just the text.
I've tried doing a repair of Outlook. I've uninstalled and reinstalled Firefox 19. I've tested dragging items from the desktop to the e-mail and it works fine. I can't drag and drop from the Downloads window to the desktop.
I just wanted to add this user is using Windows XP Pro.
bsailors trɔe
Ŋuɖoɖo si wotia
I just tried rolling it back to 18 and it works fine.
As for your question Xtinch, I've tried disabling all addons in Outlook and in Firefox and the issue still happens. I'm very convinced at this point that it's a bug in Firefox 19-20.
Xle ŋuɖoɖo sia le goya me 👍 0All Replies (11)
file:%Downloads%\randomfile.pdf is a file protocol link to the folder set with the %Downloads% environment variable and apparently the PDF file is named randomfile.pdf (if you didn't changed the real name to randomfile.pdf).
If you want the original download link the use the right-click context menu instead.
Note that in the classic download manager window you can drag the file to the Search field in that window and use Ctr+A and Ctrl+C to copy the link to the clipboard.
Sorry I obviously did a poor job in describing the problem.
Under normal circumstances, and the result I'm looking for, I want this user to be able to drag a pdf downloaded in Firefox to an e-mail in Outlook, and it automatically attach the file to the e-mail; NOT print out the text within the e-mail body.
Right now when you drag a PDF from the Firefox Download window into the body of the Outlook e-mail it creates a line of text in the body of the e-mail giving the file location.
file:///C:/DOCUME~1/dshandry/LOCALS~1/Temp/CITE%20Events%20--%20Order%20Confirmation%20-%20Hargrove-SIBOS-POV%202-28-13.pdf
for example.
I want it to attach to the e-mail in the Attachments field of the e-mail, not just print a file location as text in the body of the e-mail.
I took two screenshots. The first is how it should look, the second is how it's showing up on the users. I realize my example is slightly flawed because I had to use the file that she was trying to move as the text, but hopefully it's clear what I'm looking for.
bsailors trɔe
I have the same problem since last tuesday.
User were able to drag and drop a file to create an attachment from Firefox's download window to a Outlook 2010 email, then, for some reason it's start to paste the local file address in text mode instead of the file.
Drag and drop still works fine between outlook and other applications (explorer, iexplorer, chrome, etc).
Find attached and image with the issue.
I can confirm that this is an issue with the newest release of Firefox. I just upgraded my Firefox, which was previously 18.02 to 19.0 and now I'm getting the same error. It's a bug.
Does it help if you set another download location and do not use the default Downloads folder?
- Tools > Options > General : Downloads
No, I changed it to Desktop and it still did it.
I tried upgrading to the 20.01b beta and it's still there. I'm going to try to roll it back to 18 and see if that fixes it.
I've tested in other machines with the same configuration and they don't have the bug. Could it be related to a plugin or an specific office component?.
Ɖɔɖɔɖo si wotia
I just tried rolling it back to 18 and it works fine.
As for your question Xtinch, I've tried disabling all addons in Outlook and in Firefox and the issue still happens. I'm very convinced at this point that it's a bug in Firefox 19-20.
BSailors, I can confirm that downgrading to V.18 solves the issue, both in those with problems and the ones without it. Thanks for your workaround. Cheers.
I ran into the same issue, downgrading to V18 worked. Really annoying through, hope it gets patched.
With the last version, 22.0 the problem is still unsolved.