Bug 254165

Summary: Moving or hiding html toolbar resets formatting of mail being composed.
Product: [Applications] kmail2 Reporter: Metin Amiroff <amiroff>
Component: composerAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: montel
Priority: NOR    
Version: Git (master)   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Metin Amiroff 2010-10-14 16:18:39 UTC 
Version:           1.13.5 (using KDE 4.5.2) 
OS:                Linux

When composing an html formatted email, trying to move (dragging) formatting tollbar or hiding it by unchecking in Settings->Toolbars Shown->Html Toolbar resets the composed html message to plain text mode. 

Also, showing the toolbar again or moving it to its place does not return lost html formatting.

Reproducible: Always

Steps to Reproduce:
1. Set kmail to be able to send html mail.
2. While composing an html formatted mail, try moving formatting toolbar in composer window.
3. You can also try hiding toolbar from Settings->Toolbars Shown->Html Toolbar

Actual Results:  
Html formatting of mail being composed is lost.

Expected Results:  
Nothing should change, as hiding/moving formatting toolbar is only a cosmetic action.

OS: Linux (i686) release 2.6.35-22-generic
Compiler: cc
Comment 1 Laurent Montel 2010-10-15 14:56:24 UTC 
I can reproduce this bug
Comment 2 Christophe Marin 2012-01-07 23:56:40 UTC 
Valid in kmail2 with master

1/ Enable html, 
2/ RMB/ deselect "Lock toolbars position"
3/ Drag the formatting bar

The "Lose the formatting" warning is displayed when you start dragging the bar
Comment 3 Denis Kurz 2016-09-24 17:59: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 22:45:57 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.