115155 - Adding new filter does not get inserted properly

Status: RESOLVED DUPLICATE of bug 103684

(MailNews Core :: Filters, defect)

Description

[Sean Su]

When creating a new filter, the new filter will always get added to the top of
the filter list, instead of being inserted above the currently highlighted filter.

Steps to reproduce:
1) open the filters dialog
2) make sure there is more than one filter.
3) select the last filter (single click it) in the filter list.
4) click on the 'New' button.
5) after creating a filter rule, click the 'OK' button.

Notice that the new filter is inserted at the top of the filter list.  This used
to insert above the currently highlighted filter.  This makes it very difficult
to create a new filter and order it properly.

The workaround is to use the 'Move Up'/'Move Down' buttons, but this can be
cumbersome if the filter list is huge.

There's also a compounding problem that clicking on the 'Move Up'/'Move Down'
buttons causes the entire filter list to be (what it looks like) 'reparsed' or
refreshed?

Comment 1

[(not reading, please use [e-mail] instead)]

mass re-assign.

Comment 2

[Mike Cowperthwaite]

Is there a spec that says the new filter should be above the highlighted one?
If not, this is actually an RFE.

I am not seeing the "refresh" symptom mentioned in the last paragraph of the 
report.

Comment 3

[Andrew M. Shaw]

(In reply to comment #2)
> Is there a spec that says the new filter should be above the highlighted one?
> If not, this is actually an RFE.

Could be.  However, since the order of the list is important, there's already
a notion of "current filter", and apparently it worked that way once upon a
time, it seems like a reasonable thing to do.

> I am not seeing the "refresh" symptom mentioned in the last paragraph of the 
> report.

Long gone, though at the time it made the previous issue not just unpleasant
but down right intolerable.

Comment 4

[Howard Chu]

This looks like a dup of bug #103684

Comment 5

[Mike Cowperthwaite]

I agree, a dupe.

*** This bug has been marked as a duplicate of 103684 ***