Closed
Bug 219344
Opened 22 years ago
Closed 22 years ago
Turn ON Quote-Level Colors (Text & Background) by default
Categories
(Thunderbird :: Preferences, enhancement)
Thunderbird
Preferences
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 851022
People
(Reporter: Peter, Assigned: mscott)
Details
Quote-Level Colors are very useful in quickly identifying the portions of an
e-mail or newsgroup post that are NOT quoted, and thus what one is most likely
immediately interested in reading. Quote-Level Colors also are a tremendoud aid
in identifying the various quote-levels, thus making it easier to see who wrote
what.
Since some people may find Quote-Level Colors distracting or undesirable, these
default settings should be chosen to be as unobtrusive as possible (no "wacky"
colors).
Also, there should be an easy way to change and remove the Quote-Level Colors.
This should be covered in bug 179578.
The easiest way to do this now (so we don't have to wait for bug 179578) is to
implement the settings outlined here:
http://texturizer.net/thunderbird/tips.html#app_quotelevels and perhaps add a
setting to prefs:
+-------------------------------------------------+
| When displaying quoted plain text messages: |
| ( ) Use one setting for all quote levels |
| Style:[Regular] Size:[Regular] Color:[Blue] |
| (x) Use predefined multiple quote levels. | <-- new default
+-------------------------------------------------+
Alternatively, this bug could be used to simply add the above pref, but not make
it the default.
Suggested Settings:
/* Quote Levels Colors */
blockquote[type=cite] {
color: navy !important; background-color: RGB(245,245,245) !important;
}
blockquote[type=cite] blockquote {
color: maroon !important; background-color: RGB(235,235,235) !important;
}
blockquote[type=cite] blockquote blockquote {
color: green !important; background-color: RGB(225,225,225) !important;
}
blockquote[type=cite] blockquote blockquote blockquote {
color: purple !important; background-color: RGB(215,215,215) !important;
}
blockquote[type=cite] blockquote blockquote blockquote blockquote {
color: teal !important; background-color: RGB(205,205,205) !important;
}
Comment 1•22 years ago
|
||
*** This bug has been marked as a duplicate of 90315 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•22 years ago
|
||
This is not a dupe of bug 90315. This bug is to have Quote-Level Colors
(non-editable in UI) turned on *by default*, the other bug is to have a UI for
*editig* the Quote-Level Colors.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Summary: Use Quote-Level Colors (Text & Background) by default → Turn ON Quote-Level Colors (Text & Background) by default
Comment 3•22 years ago
|
||
No, it's not. As I said there, the other bug is also about the default.
Comment 4•22 years ago
|
||
Would be nice, if you first read before you react. Dup again.
*** This bug has been marked as a duplicate of 90315 ***
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 5•22 years ago
|
||
(OT)
Ben, I did read your explanation (actually, it wasn't really an "explanation"),
I just don't agree with it.
That bug was filed over two years ago. Due to the level of effort required to
fix it, it may be another two years before it is fixed. This bug can
(relatively) easily be fixed NOW. This bug is an attempt to achieve the desired
behavior NOW. Also, this is a Thunderbird bug, the other is mozilla, so there
are different developers with different priorities/interests working on it.
Once the other bug is fixed (likely in some distant future), they can either use
the defaults decided on here, or reconsider the issue. If (in the unlikely
event) the other bug gets fixed first, then this bug can simply be marked FIXED,
WORKSFORME or even DUPLICATE.
Unless you plan on implementing the other bug yourself soon, please do not dupe
this bug against it. Now if Scott or ASA think this is a dupe, then so be it.
(/OT)
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 6•22 years ago
|
||
> Due to the level of effort required to
> fix it, it may be another two years before it is fixed.
Nobody said that a bug has to be implemented fully to do anything at all. If the
other bug coveres default and prefs UI, and you want to do defaults only first,
that's still the other bug, just the first step of it.
> This bug can (relatively) easily be fixed NOW.
This is not clear yet. Some people may dislike the colors and complain, if you
force certain colors on them.
If that's not the case, I'd say that we may not need any prefs UI at all.
That's why IMHO the other bug is more appropriate for this discussion.
And if you split out parts of a bug to a new bug, you should in any case
reference the bugs in *both* directions. You didn't mention the other bug here
at all.
This bug is covered by the other bug, and it's thus a dup.
> Now if Scott or ASA think this is a dupe, then so be it.
Why only these 2 people? This is *my* feature, after all, I implemented it.
Updated•22 years ago
|
QA Contact: asa
Reporter | ||
Comment 7•22 years ago
|
||
Now that bug 90315 has evolved to take on some clear goal, this is truly a dupe.
*** This bug has been marked as a duplicate of 90315 ***
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•