Closed Bug 1733597 Opened 3 years ago Closed 1 years ago

With Multiple Folder Views (eg Favorites+All) - View jump to top (auto scroll up) when creating new IMAP folder

Categories

(Thunderbird :: Folder and Message Lists, defect)

Thunderbird 91
All
Windows 10
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: richard.leger, Unassigned)

References

Details

As per bug reported on https://thunderbird.topicbox.com/groups/ux/T7fc6edcd67c12957/multiple-folder-views-available-on-daily

"...
Just noticed a small issue with Multiple Folder Views in TB 91.x branch... If I enable the Favorites view and place it on the top, when I create an IMAP folder in the All folder view very down the tree... as soon a the folder is created, the view jump all the way to the top (scroll all the way up) so I lost access to the folder just created and have to scroll all the way down again manually to access it and be able to move emails into it by drag/drop.

The same happens when a folder is deleted.
..."

"...Does this happen also if you only have a single folder view currently active?..."

No.

Flags: needinfo?(alessandro)

Thanks for filing the bug.
I'll take a look at it.

Assignee: nobody → alessandro
Flags: needinfo?(alessandro)
Blocks: tb91found

Thomas, this doesn't happen with the new folder tree, right?

Assignee: alessandro → nobody
Flags: needinfo?(bugzilla2007)

(In reply to Alessandro Castellani [:aleca] from comment #2)

Thomas, this doesn't happen with the new folder tree, right?

No, I'm not seeing that with Daily 115.0a1 (2023-05-15) (64-bit), Win10.
Focus/selection remains on the parent folder from which the New Folder action is triggered, no jumps.
New folder won't be scrolled into view either, but if we keep focus/selection on parent folder by design, that's probably OK (as possibly scrolling focused/selected parent folder out of view wouldn't be right).

Flags: needinfo?(bugzilla2007)
Status: NEW → RESOLVED
Closed: 1 years ago
Hardware: x86_64 → All
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.