Scope and context affecting filter capability

NEW
Unassigned

Status

--
enhancement
10 years ago
7 years ago

People

(Reporter: beckley, Unassigned)

Tracking

({uiwanted})

Trunk
uiwanted

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [filter-mgmt])

(Reporter)

Description

10 years ago
The values in the fields of the filter editing UI (Filter Rules dialog) is currently constrained by the type of the account that the filter belongs to (also called scope).  Scope is *what* you are operating on (e.g. an offline mail store like Local Folders, an online mail store like IMAP, NNTP news groups, etc.).

There's another dimension to filtering, which is context.  Context is *when* you are performing the operation (e.g. when mail is being downloaded from the server or when the user manually asks to filter messages).  The context of filtering is currently being upgraded to include when outgoing messages are sent, as well as being able to control which of the various contexts a particular filter can be applied.

It would be good to come up with a UI that could incorporate all of these issues while editing filters.  The combination of scope and context affect what matching capabilities are available, and what actions can be performed.

This originally came out of the addition of per-filter selectable context in bug 440635.
(Assignee)

Updated

10 years ago
Product: Core → MailNews Core

Updated

10 years ago
Keywords: uiwanted

Comment 1

7 years ago
rkent, 
Is there something still worth pursuing here?  
And a practical set of steps to move this forward?
Severity: normal → enhancement
Whiteboard: [filter-mgmt]
You need to log in before you can comment on or make changes to this bug.