Open Bug 1834656 Opened 11 months ago Updated 6 days ago

Improve the elastic resizing of the tree view columns

Categories

(Thunderbird :: Folder and Message Lists, enhancement, P3)

Thunderbird 115
enhancement

Tracking

(thunderbird_esr102 unaffected, thunderbird_esr115 wontfix)

Tracking Status
thunderbird_esr102 --- unaffected
thunderbird_esr115 --- wontfix

People

(Reporter: aleca, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [Supernova3p])

When resizing the tree view columns a fixed width value is set: https://searchfox.org/comm-central/rev/5391ea879779884999142a67920e99c83ea356bd/mail/base/content/widgets/tree-view.mjs#2083

This works okay as it doesn't allow to resize columns outside the limits of the table layout, but unfortunately it doesn't work as well as 102 used to.

The old XUL tree had a more "elastic" behavior in which a flex value was set on the columns in order to let them grow or shrink based on the size of the viewport or the application.
That allowed a more natural proportional sizing of the columns.

It would be nice to emulate that behavior and improve the experience of our tree view columns.

Version: unspecified → Thunderbird 115

This is something that we will explore during this cycle to improve the general usability of the tree view, but it something that requires more thinking and prototyping so for now we're going to put it in the backlog.

Assignee: leftmostcat → nobody
Severity: -- → N/A
Priority: -- → P3
See Also: → 1843014
See Also: → 1848106
See Also: → 1850677
Duplicate of this bug: 1854705
Duplicate of this bug: 1853363
Duplicate of this bug: 1850677
Duplicate of this bug: 1855116
Duplicate of this bug: 1856252
Duplicate of this bug: 1868163

TB 115.9.0

I have tried to comprehend how the column positioning is supposed to work, without success. Nor do I understand why it has been made so complicated. I adjust one column and other columns resize on their own. Sometimes column positioning tracks the mouse, other times not. Sometimes the changes are saved, other times not; it seems to depend on the selection of en-/disabled columns.

Is there an option somewhere that reverts this function to some mindlessly simple column positioning?

You need to log in before you can comment on or make changes to this bug.