Talk:Signature display color: Difference between revisions
From MozillaZine Knowledge Base
Jump to navigationJump to search
(new CSS override rules) |
(added reference to corresponding bug for SeaMonkey) |
||
| Line 6: | Line 6: | ||
This will also be needed if you specify a "color:" along with it. Also, there is no longer a separate rule for links, the opacity applies to the selected colors for both of those. Note that the old rules may still apply to SeaMonkey, thus don't delete them for now. --[[User:Rsx11m|Rsx11m]] 22:45, 27 March 2013 (UTC) | This will also be needed if you specify a "color:" along with it. Also, there is no longer a separate rule for links, the opacity applies to the selected colors for both of those. Note that the old rules may still apply to SeaMonkey, thus don't delete them for now. --[[User:Rsx11m|Rsx11m]] 22:45, 27 March 2013 (UTC) | ||
: Corresponding bug filed for SeaMonkey [https://bugzilla.mozilla.org/show_bug.cgi?id=855684]. --[[User:Rsx11m|Rsx11m]] 14:22, 28 March 2013 (UTC) | |||
Revision as of 14:22, 28 March 2013
Thunderbird 22.0 (thus hitting the releases with 24.0 [1]) extents the display-color preferences UI to match that of Firefox [2]. As a consequence, signature and its link colors will no longer be constants but deemphasized by opacity [3], assuming that patch checks in as proposed. Thus, the respective userContent.css will be;
.moz-txt-sig, .moz-signature {
opacity: inherit !important;
}
This will also be needed if you specify a "color:" along with it. Also, there is no longer a separate rule for links, the opacity applies to the selected colors for both of those. Note that the old rules may still apply to SeaMonkey, thus don't delete them for now. --Rsx11m 22:45, 27 March 2013 (UTC)
