231305 - Drag & drop of image in page to ext app result in truncated/empty file

Status: RESOLVED DUPLICATE of bug 265720

(Firefox :: Shell Integration, defect)

Description

[Yann Coupin]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031208
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031208

When draging an image from mozilla to an external app, for instance an image
viewer or a shell (tested with total commander http://www.ghisler.com/ ) it
seems that the notification of drop to the external program is done before the
file is entirely copied onto it's temporary location. This results in either an
empty file dropped (with total commander, I haven't even got an incomplete file
with it), or either an empty file or truncated one with my image viewer. In the
second case, I've tried to reread the file from inside the viewer and the second
attempt then loads the complete image. This leads me to think that the call is
done too early. I've not been able to reproduce the problem when I drop the file
onto the desktop, but since windows explorer is a lot slower than the two
proggies before mentioned, I suspect it either receives the notification via a
different way than a standard app or it is either too slow to start copying the
file before the copy is finished. The second reason that makes me think it's
because it's too slow to get a partial file, is that if the file is small enough
(tested with a 5kB gif) I don't see the problem whichever app I use.

Reproducible: Always

Steps to Reproduce:
1. Drag an image from mozilla onto an external app (an image viewer for instance)

Actual Results:  
The file loaded in the viewer isn't complete, it misses the end. Reloading the
file resolves the problem. Retrying to drop the file doesn't solve the problem
as another truncated file is created.

Expected Results:  
The file should load complete

Comment 1

[Yann Coupin]

There's been no activity on this bug for a long time (but it's still here in
Firefox 1.0.7). Could this be in fact a dupe of bug#267426 ? The main reason for
this bug to exists beeing windows explorer is slow while programs like total
commander are much quicker to react and exhibit more easily the bug ?

Comment 2

[Yann Coupin]

I still see this behaviour using Firefox 1.5.0.4 and at least three external programs : Total Commander, XnView and The Gimp.

Can't somebody else try to confirm this bug ? It's been open for quite a while now.

Comment 3

[Yann Coupin]

Just tried with FF 2.0 RC1 using a brand new profile without any extension and I still have the same problem. Can't somebody try to reproduce this one ? I have a 100% reproducibility rate on this one...

Comment 4

[Craig Clawson]

I can confirm issue with this.  

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

As for Yann Coupin's comments of 2005-10-14 about this possibly being a dub of - I believe they are related, but not the same issue.  

Test case:
1) Open FF to: http://www.mozilla.com/en-US/firefox/central/firefox-central-title.png
2)Open Paint, or similar program
3) Drag image from page into program.
4) Receive error stating that the firefox-central-title.png file is not found in  Docume~1\$profile\LOCALS~1\Temp\

I tried this using paint, and Windows Picture and Fax Viewer.  Drag&Drop to Desktop works fine, however.

Comment 5

[[e-mail]]

However, works for me - as well on
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1) Gecko/20061010 Firefox/2.0

Comment 6

[Robin Monks]

This bug is an apparent duplicate of Bugzilla bug 265720 because:
A) Steps to reproduce of both bugs is similar and/or identical and/or the steps
to reproduce of this bug is a portion of the steps to reproduce of
aforementioned bug.
B) The aforementioned bug has more activity.
C) This bug meets the minimum requirements to be marked as a duplicate under
http://www.mozilla.org/quality/help/screening-duplicates.html.

Bug Reporter, if you feel this was done in error PLEASE REOPEN!  We're only
human here and bugs occasionally are mismarked.

*** This bug has been marked as a duplicate of 265720 ***

Comment 7

[OstGote!]

It is fixed on Trunk (FF 3.0/SeaMonkey 1.5) by bug 267426.