Bug 354448 - Window resize resizes left side bar instead of main content pane (message preview pane)
Summary: Window resize resizes left side bar instead of main content pane (message pre...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-27 10:27 UTC by moenshendrik
Modified: 2018-01-31 16:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description moenshendrik 2015-10-27 10:27:45 UTC
I'm using "short folder list" and "show the message preview pane next to the message list" in the kmail layout options.

When resizing the window, the left sidebar increases in size, while in this layout it would be expected that the size of the message preview pane would change. This behaviour is very annoying as I frequently resize and always have to readjust the sidebar width (when maximizing the window this behaviour can cause the sidebar to take up up to 70% of the total width of the application).

Reproducible: Always

Steps to Reproduce:
1. Open kmail
2. Set "show short folder list" and "show message preview pane next to the message" in setting (Configure > Appearance > Layout)
3. Resize the window

Actual Results:  
The side bar increases and decreases in size. When the window is made very small (e.g. using window tiling) and is then maximized, the side bar takes up a huge portion of the window.

Expected Results:  
The sidebar size remains the same, and the content pane increases in size (preferred)
OR
Both the content pane and sidebar resize relative to their respective size
Comment 1 Denis Kurz 2017-06-23 20:21:31 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-01-31 16:51:45 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.