Bug 106506 - [Import/Export] Import Dialog initial size too wide to read long file/folder names
Summary: [Import/Export] Import Dialog initial size too wide to read long file/folder ...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows 2000
: P5 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-08-09 11:52 EDT by Karice McIntyre CLA
Modified: 2019-09-06 15:36 EDT (History)
0 users

See Also:

Attachments
pic of filename truncated in tooltip (59.36 KB, image/jpeg)
2005-08-09 12:04 EDT, Karice McIntyre CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Karice McIntyre CLA 2005-08-09 11:52:10 EDT 
Win2k (but prob all platforms), I20050808-2000, Arabic

Export dialog opens to full screen when project has long file/folder name at 
top directory-level

*Create a Simple Project
*Create a file and a folder with a very long name
*Select the project, File > Import/Export, select Export tab
*Choose one of either Export > File System or Export > Archive File, click Next
notice: the dialog takes the full screen width which is ok in LtR languages 
because you can hover over the file/folder name and see it all in the tooltip, 
BUG: in RtL languages you will not be able to see the full file name because 
the panes are flipped
Comment 1 Karice McIntyre CLA 2005-08-09 12:04:18 EDT 
Created attachment 25909 [details]
pic of filename truncated in tooltip
Comment 2 Karice McIntyre CLA 2006-07-05 17:23:17 EDT 
This is not strictly a Bidi problem.  If you are running Eclipse in English and create a project or a folder or a file with a really long name, then do Export > File System you will see the same problem.
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:36:43 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.