We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

সহায়তা খুঁজুন

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

আরও জানুন

Drag and drop files from folder to open email in firefox

  • 2 উত্তরসমূহ
  • 1 এই সমস্যাটি আছে
  • 4 দেখুন
  • শেষ জবাব দ্বারা epixjob

more options

Since about a month ago I can't drag a file from a folder to an open email in Firefox. Was always able to, but it stopped a few weeks ago. I read that the new 99.01 version would fix this, I installed it today and the problem persists. What am I missing? Thank you to anyone who reads, cares and replies with solution.

Since about a month ago I can't drag a file from a folder to an open email in Firefox. Was always able to, but it stopped a few weeks ago. I read that the new 99.01 version would fix this, I installed it today and the problem persists. What am I missing? Thank you to anyone who reads, cares and replies with solution.

All Replies (2)

more options

Is this about dragging a file in Outlook (OWA) ?

This is probably something MS needs to be done on their side. A possible workaround for now is to attach the files instead of dragging.

(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
)

cor-el দ্বারা পরিমিত

more options

Hi cor-el, thank you for your input and trying to troubleshoot this problem. When OWA is open in Microsoft Edge there is no problem with drag and drop a file from a folder to an open email. It only happens with OWA open in Firefox. I thought upgrading to 99.01 would fix this, but it did not. In regards to work around, yes that is what I'm now doing, attaching files through the email menu, but this is fastidious and slow, I prefer and find it much faster to use drag and drop. I'm surprised there aren't more people with this issue or that Mozilla has not noticed or addressed this issue...