517848 - While collapsing the folder pane, make sure that it doesn't get reduced to its minwidth in other tabs

Status: RESOLVED INVALID

(Thunderbird :: Mail Window Front End, defect)

Description

[Rain [:rain1] (inactive)]

from bug 517244 comment 5. I agree that it's annoying.

Comment 1

[David Ascher (:davida)]

Annoying, but I don't think blocking.

Comment 2

[Mark Banner (:standard8)]

To be clear the issue is:

> One unfortunate situation that happens on linux is that because there is no
> single-click-to-collapse behavior on the splitter, I have to drag the folder
> pane closed.  Because the splitter's position is updated as I drag it, dragging
> the folder pane closed actually has 2 results:
> 
> 1) The folder pane gets collapsed on the current tab.
> 2) The folder pane gets shrunk to its minimum size.  This affects all tabs
> where the pane is still visible.

Comment 3

[Wayne Mery (:wsmwk)]

dup of bug 340982, but if I'm wrong, please make the correction

Comment 4

[Rain [:rain1] (inactive)]

This issue is related to, but different from that one.

Comment 5

[Wayne Mery (:wsmwk)]

Attachment: folder pane wierdness

is this bug linux-only?

related in any way to this wierdness?  If I drag splitter to the right from fully collapsed state I see 
1) total lameness in the thread pane (scrollbar near left)
2) folder names exceed splitter
3) the only place I can grab splitter is between the folder pane header and the thread pane header

Comment 6

[Wayne Mery (:wsmwk)]

(In reply to comment #5)
> Created attachment 490611 [details]
> folder pane wierdness
never mind, this is more related to  bug 340982. 
caused by folder pane width being narrower than header of the folder pane.

but, is this bug 517848 linux-only?

Comment 7

[Rain [:rain1] (inactive)]

No, I can reproduce on Windows too.

Comment 9

[Michael Nüsken]

Actually, it seems that the folder pane width is modified for all tabs with every update.
Collapsing it in one tab, reduces it to a minimum in other tabs. Changing it in one tab, modifies it elsewhere too.
Even though this is a minor issue, it would be nice to have this repaired eventually.

Comment 10

[Wayne Mery (:wsmwk)]

If this is still seen in version 115, which has new code, please file a new bug.