Closed
Bug 366575
Opened 19 years ago
Closed 19 years ago
No U.I. for X-Priority "None": Compose / Filter / Search.
Categories
(MailNews Core :: Composition, defect)
MailNews Core
Composition
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: sgautherie, Unassigned)
Details
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a2pre) Gecko/20070109 SeaMonkey/1.5a] (nightly) (W2Ksp4)
In Compose window Priority menu, and Filter U.I., and Search U.I., ..., there is no item for "None".
Yet, "None" is the default value "used" to send (or receive) message without the X-Priority header.
Then, I suggest to add a "None" value, as the default, to these lists.
This is both:
*a bugfix, as it would add consistency, at least to the compose window;
*an enhancement, as it would allow to "unselect" a priority when composing, and filter/search for messages without priority.
I filed this under "Mailnews: Composition", but it applies to "Filter" and "Search" too.
Updated•19 years ago
|
OS: Windows 2000 → All
Hardware: PC → All
Comment 1•19 years ago
|
||
> Yet, "None" is the default value "used" to send (or receive) message without
> the X-Priority header.
No. In the absence of an explicit X-Priority header, the assumed default is "Normal". Actually, you should not _send_ Normal at all, but leave the header out in that case. You have to recognize it, though.
> *a bugfix, as it would add consistency, at least to the compose window;
No - why should this add consistency? There's no priority value "None".
> *an enhancement, as it would allow to "unselect" a priority when composing,
> and filter/search for messages without priority.
No - to reset, just choose "Normal".
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Updated•18 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•