Bug 314872

Summary:	creating a new message resets the font size in signature to the message font size
Product:	[Applications] kmail2	Reporter:	Liviu Vasut <liviu.vasut>
Component:	composer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	montel
Priority:	NOR
Version:	4.9.5
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Liviu Vasut 2013-02-11 06:56:59 UTC

I have a HTML signature with font size of 10. Message body font size is set to 12. When I click the "New" mail button a window opens with the message body ready to be filled in and the signature appended. The signature font size should be 10 not 12.

Reproducible: Always

Steps to Reproduce:
1. create a HTML signature (Settings > Configure KMail > Identities > (select account) Modify... > Signature > check "Enable signature" and choose "Input Field Below" from the "Obtain signature text from:" field. Enter signature and set font size to 10)
2. set message body font size: (Settings > Configure KMail > Appearance > Fonts > check "Use custom fonts", select "Message body" from the "Apply to:" field and set the font size to 12)
3. Create a new message (click "New" button on the tool bar)
Actual Results:  
font size in the signature is the same as in the message body

Expected Results:  
font size in the signature should be 10 (as set)

Keep the font settings from the signature dialog

Comment 1 Laurent Montel 2013-02-11 13:05:48 UTC

I confirm it.
It's when we don't set font when created signature.
We must for font size.

Comment 2 Denis Kurz 2016-09-24 18:14:28 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 3 Denis Kurz 2017-01-07 22:32:58 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.