Closed
Bug 447746
Opened 17 years ago
Closed 17 years ago
Rename Folder rejects case changes
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
People
(Reporter: danforth, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Build Identifier: version 2.0.0.14 (20080421)
It is not possible in one step to rename a folder which only changes the case of the folder name. The error message generated is
"A folder with that name already exists. Please enter a different name."
For example:
Innocentive => InnoCentive
One must do a two step process
Innocentive => grabage
garbage => InnoCentive
I consider this bad design and a definite bug.
Best regards,
Douglas G Danforth, Ph.D.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Expected Results:
One should in one step be able to rename a folder which just a case change
e.g.
Innocentive => InnoCentive
This is a design flaw where, I assume, the input is converted to, say, lowercase, and then compared to all folder names also in lower case BUT the actual displayed name is not converted.
Hence one needs to remove the conversion step for folder name comparisons.
This allows there to be multiple folders with names such as
ABC
ABc
AbC
Abc
etc.
I'm experiencing the same behavior as described above, i.e. I need to run a two step rename process.
However, in contrast to the above proposal I wouldn't go as far as making folder names case-sensitive. Without having looked at the code I would suggest to simply drop the folder which is currently being renamed, from the list of existing folders, essentially by-passing the comparison to the same folder name. Just a suggestion and it might not even prove to be a good one after taking a look at the code...
Updated•17 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Comment 3•17 years ago
|
||
V.Duplicate
Severity: normal → minor
Status: RESOLVED → VERIFIED
Version: unspecified → 2.0
You need to log in
before you can comment on or make changes to this bug.
Description
•