Bug 310601

Summary: "Reset font settings" doesn't reset to Plain text
Product: [Applications] kmail2 Reporter: Bernd Oliver Sünderhauf <pancho.s>
Component: composerAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: montel
Priority: NOR    
Version: 4.9.3   
Target Milestone: ---   
Platform: Chakra   
OS: Linux   
Latest Commit: Version Fixed In:

Description Bernd Oliver Sünderhauf 2012-11-24 13:03:43 UTC
Even if the "Reset font settings" button wipes away HTML formatting, for some reasons the mail still gets sent as HTML.
To reproduce it with a very simple one-word mail:

1. Compose a new message with the word "Test"
2. Mark the text

Scenario A:
3. Don't do any formatting.
4. Send to yourself
=> received as Plain text = okay

Scenario B:
3. Don't do any formatting.
4. Reset font settings (superfluous)
5. Send to yourself
=> received as Plain text = okay

Scenario C:
3. Format bold
4. Send to yourself
=> received as HTML = okay

Scenario D:
3. Format bold
4. Reset font settings
5. Send to yourself
=> received as HTML = wrong

Scenario E:
3. Format bold
4. Unformat bold
5. Send to yourself
=> received as Plain text = okay

Scenario F:
3. Format bold
4. Unformat bold
5. Reset font settings (superfluous)
6. Send to yourself
=> received as Plain text = wrong

Obviously, "Reset font settings" doesn't reset a composed mail to Plain text, even if no formatting remains (scenario D).
Even more, if any formatting has ever been applied to the composed mail, "Reset font settings" forces the mail to be send as HTML, even if no formatting remained.
Comment 1 Laurent Montel 2012-11-25 10:13:57 UTC
I confirm it Will look at it
Comment 2 Laurent Montel 2012-11-25 10:33:12 UTC
Will fix tomorrow morning. Find bug.
Thanks
Comment 3 Denis Kurz 2016-09-24 18:12:23 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 4 Denis Kurz 2017-01-07 21:37:03 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.