File copy via DnD in front end destroys file (zero length)

google-code-export / yabi

Automatically exported from code.google.com/p/yabi

0 stars 1 forks source link

File copy via DnD in front end destroys file (zero length) #212

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. login to front end
2. go to file tab
3. pull up two different directories.
4. drag a file from the left pane to the right

What is the expected output? What do you see instead?
Front end says "copying finished" but it doesn't copy. In fact it destroys the 
source file by trying to copy it on top of itself. Source file gets truncated 
to zero bytes.

No matter what the drop target pane is, it always tries to copy to itself. As 
if you drop on the same pane as the source. This copies the file over itself, 
destroying it in the process. Firstly, a drag from a pane, to the same pane, 
should not attempt to do anything (unless you're dropping it into a folder). 
Secondly, even if you drop it in a different pane, it still copies it over 
itself

Original issue reported on code.google.com by retrogra...@gmail.com on 12 Jun 2012 at 4:42

GoogleCodeExporter commented 9 years ago

Original comment by retrogra...@gmail.com on 12 Jun 2012 at 4:43

Added labels: Priority-Critical
Removed labels: Priority-Medium

GoogleCodeExporter commented 9 years ago

Seems to work for me. Chrome on ubuntu.

Original comment by amacgregor on 12 Jun 2012 at 4:50

GoogleCodeExporter commented 9 years ago

works now for me I rebuilt it all. But will try and recreate. May be post-test 
suite that the effect occurs.

Original comment by retrogra...@gmail.com on 12 Jun 2012 at 5:09

Changed state: New

GoogleCodeExporter commented 9 years ago

Works for me too. Firefox on Ubuntu. It is all JS so maybe you had some old JS 
cached.

The first issue - copying to the same pane shouldn't do anything - I think I 
just ported from the previous version, wasn't it always like that?

I do agree that we shouldn't do anything if the source is the same as the 
destination though, so maybe a separate ticket for that issue would be a good 
idea so we can prioritise it etc.

Original comment by szab...@gmail.com on 12 Jun 2012 at 5:12

GoogleCodeExporter commented 9 years ago

yeah. checked again. Checked post fab tests. All works ok. Must have been some 
stale JS. I'll reopen this if I experience it again.

Original comment by retrogra...@gmail.com on 12 Jun 2012 at 6:27

Changed state: Invalid