Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 347015

Summary:	[client] copy/rename file prompt shows clipboard content on FF4, failure to copy not reported
Product:	[ECD] Orion	Reporter:	Susan McCourt <susan>
Component:	Client	Assignee:	Susan McCourt <susan>
Status:	RESOLVED NOT_ECLIPSE	QA Contact:
Severity:	normal
Priority:	P3
Version:	0.2
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Susan McCourt

2011-05-24 12:11:08 EDT

running orion.eclipse.org (20110516).
I used ctrl-c, ctrl-v to copy a file in place.
The rename prompt gave me the full path of the file as the default new name.

So I changed the name and hit enter.
Nothing happened, no error reported.

Two problems:
1) the new name is supposed to be "Copy of OldName" without a full path (I could have sworn I implemented this)
2) the failure is not being reported correctly

Comment 1 Susan McCourt

2011-05-25 20:40:58 EDT

(In reply to comment #0)

> Two problems:
> 1) the new name is supposed to be "Copy of OldName" without a full path (I
> could have sworn I implemented this)

This is implemented correctly.  The problem is that on FF4, the clipboard contents are shown in the window.prompt box instead of the parameter passed into the method.  I suspect this broke with FF4, because I've been running FF all along and this used to work.  It's working properly still in Chrome. 

The reason I thought the problem was a full path name issue was simply because I had a path in my clipboard at the time!

> 2) the failure is not being reported correctly

Still true, and this seems the more important bug for June, since we can actually fix it.

Comment 2 Susan McCourt

2011-05-26 11:39:49 EDT

weirdness.  I had to kill and restart FF4 and then problem #1 went away. (!)

Comment 3 Susan McCourt

2011-06-08 23:05:15 EDT

I have not seen problem #1 since first reported.  When I saw it, I had been running FF4 for quite some time and performance was very degraded.  So I really believe this to be a FF4 bug, since we are talking about window.prompt and since it works in most observed cases.

Problem #2 was already addressed in bug 348149