All users were logged out of Bugzilla on October 13th, 2018
In the message index window, message with high priority are not "red higlighted" as in the version 0.9.1 Is it normal?
Confirming 2001070404 WinMe
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: message with high priority → message with high priority not colored red
I believe coloring is removed intentionally.. whether that be a good thing is another matter. See bug 81085.
Yeah, it's intentionally. It's only displayed in the Priority *column* if you have that visible.
*** Bug 121223 has been marked as a duplicate of this bug. ***
Now we've removed all color for Priority, even in the column. This was done to avoid clashing with the Label feature, which uses color highlighting and text.
Laurel, I find that the only "Highest" word in the priority column doesn't assure the importance viewing of the message. Moreover, if the user hasn't the column at all, he will have no idea of the priority (and the related importance gaved by the sender) itself. Then consider the majority of users use mail program that have "priority" as set, and not labelling I think Mozilla might use not to colouring messages, because the method is now used by Labelling system, but put a small icon (i.e. and esclamation mark) near to the title, when it has high or highest priority (note Outlook uses only "high"). And it should be undeletable by user. This is pretty viewable and is according with major mail client interfaces, that uses to put a "!" near to high prioriry emails. --luciano
1. can the reporter get what he wants w/ userChrome.css? 2. could we have a filter which set the label
As previously discussed here, we can't use colors because they conflict with the new labeling mechanism. Opened bug 124068 to investigate alternatives for showing message priority that don't conflict with labeling.
This is invalid since we implemented labels -- no color coding specific to priority anymore.
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.