Bug 228108 - [Wizards] leading whitespaces in file names
Summary: [Wizards] leading whitespaces in file names
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3.2   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-21 17:04 EDT by Raj Alagumalai CLA
Modified: 2019-09-06 16:07 EDT (History)
6 users (show)

See Also:

Attachments
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 Raj Alagumalai CLA 2008-04-21 17:04:11 EDT 
Build ID: Build id: M20080221-1800

Steps To Reproduce:
currently it's possible to create "abc.txt" and " abc.txt"

not sure if this should be allowed
Comment 1 Raj Alagumalai CLA 2008-04-21 17:04:51 EDT 
I see the same behavior in 3.4 too

Eclipse SDK

Version: 3.4.0
Build id: I20080330-1350
Comment 2 Eric Moffatt CLA 2008-04-22 10:34:32 EDT 
While it appears that this -is- a valid name on the platform I agree that starting a file name with a blank is much more likely to be a user error than a desired result. Perhaps we should augment the validation to explicitly check for this?
Comment 3 Raj Alagumalai CLA 2008-04-23 20:31:54 EDT 
I hit this issue in the context of user error and noticed that the editor which was supposed to handle a file named weblogic.xml was not being displayed and then realized that the leading whitespace was causing this to be treated as a different file type.
Comment 4 Frank Gilchrist CLA 2008-09-19 08:25:54 EDT 
I am also seeing this in: Version: 2.4.0.v200806091234
Build id: 200807091240
Comment 5 Boris Bokowski CLA 2009-11-26 16:19:01 EST 
Prakash is now responsible for watching bugs in the [Wizards] component area.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:07:33 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.