336393 - [1.5] new directory can no longer be named with content of X-selection

Status: RESOLVED WORKSFORME

(Firefox :: File Handling, defect)

Description

[Franz]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.12) Gecko/20050920 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.12) Gecko/20050920 Firefox/1.0.7

With the current Firefoxes 1.5.x you can no longer name a new directory with the
content of the X-selection.

Reproducible: Always

Steps to Reproduce:
1. Select an arbitrage web page to save
2. Mark some text (put it in the X-selection) you want to name a directory with.
3. File | Save As | Browse Folder | Create Folder


Actual Results:  
The content of the X-selection is lost (FF "suggests" a new folder name
which is highlighted and thus overwrites the X-selection)

Expected Results:  
Paste the content of the X-selection I put in.

Comment 1

[Philip Withnall (unavailable)]

Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9a1) Gecko/20060502 Minefield/3.0a1 - Build ID: 0000000000
WFM.
Can you reproduce this in safe mode? (http://kb.mozillazine.org/Safe_Mode)

Comment 2

[Franz]

Yes, can reproduce this in safe mode.

I have observed a side effect:

If you click on "Create Folder" and then 
click on the window's title bar or somewhere else on the
desktop a new subdirectory is created namend "Ordnername eingeben" 
(German version). 

If this subdir already exists an error message shows up.

Is it possible to revert to FF 1.0's file dialog?

Comment 3

[Steve England [:stevee]]

Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!

Comment 4

[Franz]

I still do see this problem in 

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a6pre) Gecko/20070607 Minefield/3.0a6pre

Comment 5

[Franz]

Problem persiststs in 3.5.5. Seems to be a design problem in GNOME's file dlg.

Comment 6

[Manuela Muntean [Away]]

WFM with the latest Nightly (build ID: 20130825030201).

Please reopen this bug if you can still reproduce this issue.