Closed Bug 479457 Opened 17 years ago Closed 14 years ago

Sidebars collapse according to label width instead a predefined min-width

Categories

(Thunderbird :: General, defect)

Product:
Thunderbird
Component:
General
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: ShareBird, Unassigned)

Details

If you try to make any sidebar on Thunderbird narrower by dragging the sidebar splitter it will collapse immediately when the width from sidebar is equal to the label width. In Firefox (although the sidebar doesn't collapse) the label will crop and you are able to make sidebars narrower. I think this behavior is inconsistent since we don't know how wide can be a label at some localization or from some extension (we can suppose some extension could use "A very wide description for the label"). This makes difficult for user to customize the width from sidebars. This behavior is very noticeable using the theme Silvermel: https://addons.mozilla.org/en-US/thunderbird/addon/7517 since it uses a kind of letter-spacing for the labels.
Any thoughts about this issue?
I think its a reasonable change. I was actually waiting for you to propose a default value and some evidence for why it is better. Didn't mean to stall anything, sorry for the lack of response.
(In reply to comment #2) > I think its a reasonable change. I was actually waiting for you to propose a > default value and some evidence for why it is better. Didn't mean to stall > anything, sorry for the lack of response. Sorry for the long time I've needed to answer, somehow I didn't notice there were an answer on it... I think the best would be to collapse the sidebar only when its width reached a pre-determined min-width. Unfortunately I was unable to find the piece of code responsible for the collapse of the sidebar to further investigate it.
I can't see this in recent nightlies anymore. It was fixed on other bug, I suppose... Should I mark it as RESOLVED?
Yes, I believe this was fixed in bug 620638.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Very good! Thanks.
You need to log in before you can comment on or make changes to this bug.