299732 - Renaming message filter overwrites existing filter

Status: RESOLVED INCOMPLETE

(Thunderbird :: General, defect)

Description

[plache]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Thunderbird version 1.0.2 (20050317)

OS = MSW-XP / version 1.0.2 (20050317) / No Extensions

1. Define New Message Filter, name it "A", [Ok]
2. Define New Message Filter, name it "B", [Ok]
3. Define New Message Filter, keep the default name "Untitled Filter" [Ok]
4. [edit] "Untitled Filter" and change the name to "B" [OK]

At this point you have replaced the "B" filter with "B - the Untitled Filter".
And you have "A" and "B" filters.

5. [Edit] "B" and change the name to "C" [OK]

You now have (2) "C" filters,
and they are both real "C" filters (noted by content).
And you still have "A".
And at this point you have No "B" filter.

5. Delete Filter "A" and
one of the "C" become "B" the real "B" filters (noted by content).

Somehow the "B" filter came back.
And what did "A" filter have to do with this?
I never did anything with "A" except make it and delete it.
And yet by deleting "A" it made "B" come back.

Note: To keep track of these filters (with all this re-naming)
Place the Filter name in the "subject" line,
and just select "[X] Flag this message"
in the "Perform these actions:" field.


Reproducible: Always

Steps to Reproduce:
Just follow the "Details" description,
using arbitrary new names for the filters.

Actual Results:  
Filters are messed up.

Expected Results:  
Checked for conflicting filter names,
and not permitted to rename filter
to existing name.

Comment 1

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Reporter, does the issue still occur with the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported Thunderbird version 2 is 2.0.0.16)

Comment 2

[Joshua Cranmer [:jcranmer]]

RESO INCO per lack of response to the last question. If you feel this change was made in error, please respond to this bug with your reasons why.