Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

I can't drag images or file links to the Downloads window.

  • 1 antwoord
  • 3 hebben dit probleem
  • 27 weergaven
  • Laatste antwoord van betoalanis

more options

I usually browse a lot of images and large files and it's easier for me to have the Downloads window open and drag the links or images to it to start the download. This lets me keep track of the progress of each file and check the proper names. Since FF 18 I can't do this, it doesn't let me drag to this window no more. I know I can drag things directly to the Finder window (I'm on OSX 10.8.2), and this still works. But it's not the same workflow, I like to use the Downloads window better.

Here is the video that shows the bug in action: http://cl.ly/MAdj. - First I try dragging a .zip file link, then an image, and finally I drag the image to open a new tab to show that works and it's a simple image file.

Is this a general bug? a feature removed or is it just me?

I usually browse a lot of images and large files and it's easier for me to have the Downloads window open and drag the links or images to it to start the download. This lets me keep track of the progress of each file and check the proper names. Since FF 18 I can't do this, it doesn't let me drag to this window no more. I know I can drag things directly to the Finder window (I'm on OSX 10.8.2), and this still works. But it's not the same workflow, I like to use the Downloads window better. Here is the video that shows the bug in action: http://cl.ly/MAdj. - First I try dragging a .zip file link, then an image, and finally I drag the image to open a new tab to show that works and it's a simple image file. Is this a general bug? a feature removed or is it just me?

Gekozen oplossing

This has been fixed in Firefox 19 :D

Dit antwoord in context lezen 👍 0

Alle antwoorden (1)

more options

Gekozen oplossing

This has been fixed in Firefox 19 :D