Closed
Bug 517431
Opened 16 years ago
Closed 16 years ago
New message filter created with incorrect name
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 510703
People
(Reporter: deboot, Unassigned)
Details
(Keywords: regression)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.4pre) Gecko/20090915 Lightning/1.0pre Shredder/3.0b4pre
When creating a new message filter, the filter is not created with the user-specified name. It's named according to the set up rules. This might be handy if the filter name is not specified, but when the user names the filter the way he wants, it should stay that way.
Reproducible: Always
Steps to Reproduce:
1. Open message filters dialog
2. Click the 'New...' button
3. Type in a filter name, ie 'Foo'
4. Set up filter, ie 'Subject contains Bar'
5. Select some destination folder
6. Click 'OK'
Actual Results:
The newly created filter gets named 'Subject contains: Bar'
Expected Results:
The newly created filter should be named 'Foo'
Comment 1•16 years ago
|
||
confirming on Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.4pre) Gecko/20090915 Thunderbird/3.0b4
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
OS: Windows Vista → All
Hardware: x86 → All
Version: unspecified → 3.0
Comment 2•16 years ago
|
||
Sounds like a duplicate of bug 510703 the fix for which went into the tree in time for today's nightly.
Whiteboard: dupeme
| Reporter | ||
Comment 3•16 years ago
|
||
wfm in Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.4pre) Gecko/20090923 Lightning/1.0pre Shredder/3.0pre, closing resolved fixed.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•16 years ago
|
Resolution: FIXED → DUPLICATE
Comment 5•15 years ago
|
||
Cleanup *dupeme* whiteboard flag from bugs that are marked as Resolved Duplicate!
Whiteboard: dupeme
You need to log in
before you can comment on or make changes to this bug.
Description
•