Signatures & Display Color
Metallo
I followed the suggestion I found in the KB, created a signature as
follows in HTML:
Myname
Myn...@gmail.com
then created a userContent.css file and put the following code:
/*
* Change display color of text and links in signature
*/
.moz-txt-sig, .moz-signature {
color: black !important;
}
.moz-txt-sig > a, .moz-signature > a {
color: blue !important;
}
Clicked "Write" and I get everything in black.
My intent is instead:
Myname in black
Myn...@gmail.com in blue, given that this is a link
Also, I noticed after having sent the message, the recepient (myself for
testing reason) gets the signature in grey, while I would expect the
recepient to get myname in black and Myn...@gmail.com as a blue link.
Where am I wrong?
Thank you
Alex
Nir
> Hi,
>
> I followed the suggestion I found in the KB, created a signature as
> follows in HTML:
>
> Myname Myn...@gmail.com
>
> then created a userContent.css file and put the following code:
>
> /* * Change display color of text and links in signature */
> ..moz-txt-sig > a, .moz-signature > a { color: blue !important; }
>
> Clicked "Write" and I get everything in black.
>
> My intent is instead:
>
> Myname in black Myn...@gmail.com in blue, given that this is a link
>
I think you have created signature in this format
--<space><Enter><Your signature>
like
--
Myname
Myn...@gmail.com
> Also, I noticed after having sent the message, the recepient (myself
> for testing reason) gets the signature in grey, while I would expect
> the recepient to get myname in black and Myn...@gmail.com as a blue
> link.
"This changes only the way that signatures are displayed in Thunderbird
and will not affect the color of any signatures that you use with
outgoing messages. However, recipients who use Thunderbird normally see
gray signatures unless they have changed the setting too. Other mail
clients might do similar things."
Metallo
> Metallo wrote:
>> Hi,
>>
>> I followed the suggestion I found in the KB, created a signature as
>> follows in HTML:
>>
>> Myname Myn...@gmail.com
>>
>> then created a userContent.css file and put the following code:
>>
>> /* * Change display color of text and links in signature */
>> ..moz-txt-sig, .moz-signature { color: black !important; }
>> ..moz-txt-sig > a, .moz-signature > a { color: blue !important; }
>>
>> Clicked "Write" and I get everything in black.
>>
>> My intent is instead:
>>
>> Myname in black Myn...@gmail.com in blue, given that this is a link
>>
>
> I think you have created signature in this format
> --<space><Enter><Your signature>
>
> like
Yes, that's why I do no understand why the color does not match.
Isn't that correct?
Also, yesterday, the mail that I sent myself had a signature appearing
with my email address as a blue link, but I do not remember how I did it :(
Peter Potamus the Purple Hippo
the script for userContent.css only changes the display of
the sig file that is received by you. For example, take a
look at my sig file. What you see, the colors, etc, is on
your own screen. Those are the colors you set. That is
from the script. It doesn't matter what colors I sent the
message in, its what you set to display them.
The blue link is coming from
moz-txt-sig > a, .moz-signature > a { color: blue !important; }
again, that is what you have set for displaying sig files,
when they come to you. The userContent.css file over rules
the settings of what someone else sent you.
--
Please do not email me for help. Reply to the newsgroup
only. And only click on the Reply button, not the Reply All
one. Thanks!
Peter Potamus & His Magic Flying Balloon:
http://www.toonopedia.com/potamus.htm
Terry R.
Hi Metallo,
What you are adding in the userContent.css is for *your* viewing only,
not what others will see.
Blue for link color is the default color, so you don't need to add
anything there. To make your signature black, you need to /not/ use the
delimiter. Try the extension QuickText. It allows you to make many
sigs and you can use HTML if you choose.
http://extensions.hesslow.se/extension/4/Quicktext/
In Composition & Addressing, if you check "Automatically quote the
original message when replying", Then "start my reply above the quote"
and place my signature "below my reply (above the quote)", TB will not
use a delimiter and your signature will be black and the email address
will be blue, by default. This should be used for email and for
newsgroups that allow top posting.
--
Terry R.
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.
Metallo
Lets' start from the beginning:
Target: get to send out a signature as follow:
myname
myn...@gmail.com (blue)
I have deleted the userControl.css, so no worries for that.
I followed exactly the procedure to create HTML signatures in KB:
1. In Thunderbird, compose a new HTML message.
2. Type the text you want to use for your signature. Add whatever
formatting you want (font style, color, bold, etc.).
3. Select the text you want in your signature (or choose Edit –
Select All if you want the whole message as your signature).
4. Choose: Insert – HTML...
5. In the Insert HTML window, select all the text and copy it. (For
example, press Ctrl+C, or get a context menu for the text by
right-clicking it and select Copy.)
6. Open a new file in any text editor (for example, Notepad) and
paste the text you just copied.
7. Save the file, giving it a name with the .html extension—for
example: signature1.html
I would expect to get into my gmail.com account exactly what I want,
instead I get a grey signature, as if I have done it in plain text, but
I did it in HTML.
Please, note that if I send with MS Outlook my signature to my gmail
account I get exactly what I aim too, why cannot I get the same if I
send with TB?
TB has got many pros Vs MS Outlook, but signatures are a nightmare,
since yesterday I have been trying to get a simple signature to work but
still no success, certainly I cannot say this function is user friendly :(
Thank you for you help
Alex
Metallo
You know what the stupid thing it is? If you send a mail from TB with
subject and no text, signature pops up in grey, if you add a word in the
body, signature pops up as it should, that is, name in black, email
account in blue.
Sad but true TB!
Cheers
Alex
Terry R.
Alex,
Have you checked to make sure your gmail account is set to compose in
HTML? Check Tools, Account Settings, click on the gmail account
Composition & Addressing, and on the right check "Compose messages in
HTML format". If that is checked, paste in your sig HTML code here so
it can be checked. I use an HTML sig file on a couple accounts and it
works fine, so it's not a TB issue.
Brian Heinrich
> On 4/18/2007 10:49 AM On a whim, Metallo pounded out on the keyboard
<snip />
>> TB has got many pros Vs MS Outlook, but signatures are a nightmare,
>> since yesterday I have been trying to get a simple signature to work
>> but still no success, certainly I cannot say this function is user
>> friendly :(
>
> Have you checked to make sure your gmail account is set to compose in
> HTML? Check Tools, Account Settings, click on the gmail account
> Composition & Addressing, and on the right check "Compose messages in
> HTML format". If that is checked, paste in your sig HTML code here so
> it can be checked. I use an HTML sig file on a couple accounts and it
> works fine, so it's not a TB issue.
I've never had a problem with a HTML sigs, but it's been a while since I've
used one.
HTML sigs are in a <div> --
<div class="moz-signature">-- <br>
%SIG%
</div>
-- so creating an HTML sig file that looks something like this should work:
<p>Joe l'User<br />
<span style="font-family: monospace;"><<a
href="mailto:%20Joe%20l%27User%20%3Cjoe...@myisp.net%3E title="Contact me
via e-mail.">joe....@myisp.net</a>></span>
</p>
However, it's been some years since I've set up an HTML sig, so you might
need to monkey around a bit with it. . . .
--
/b.
String quartets don't march very well.
--Donald Barthelme, /The Dead Father/
JoeS
If you look at the format that was sent on your failed experiments, I think you will see that they were sent in plaintext
even though that was not your intention. TB and Seamonkey revert to plaintext if no HTML element is included in the body.
Generally speaking Gecko reverts to plaintext at the first "excuse" to do so.
JoeS
Brian Heinrich
<snip />
> Hi Alex,
> If you look at the format that was sent on your failed experiments, I
> think you will see that they were sent in plaintext
> even though that was not your intention. TB and Seamonkey revert to
> plaintext if no HTML element is included in the body.
> Generally speaking Gecko reverts to plaintext at the first "excuse" to
> do so.
Again, it's been a few years, but (IIRC) the reason I found myself playing
with HTML sigs was in order to force Moz (at the time) to send as HTML. . . .