Closed Bug 1875596 Opened 6 months ago Closed 6 months ago

When the message list is refreshed and the message list redrawn, the messages are reverted to threaded

Categories

(Thunderbird :: Folder and Message Lists, defect)

Thunderbird 115
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1725127

People

(Reporter: timb, Unassigned)

Details

Steps to reproduce:

This bug was reported before, but with inaccurate steps to reproduce.

Force the message view to be refreshed, for example, by deleting messages. It requires the message view to be refreshed (redrawn from scratch) completely to show up. Does not happen on each message delete, unless the view is completely refreshed.
With refreshed I mean, the screen is erased and then all messages are show again, but now threaded.

Actual results:

The view changes to threaded where messages are collapsed in to threads.
This bug has been introduced with one of the recent updates.
I am currently using TB 115.6.1

Expected results:

The view should have remained unthreaded.

Thanks for the update. However I don't see how this is different from bug 1864720.
Also, you do not state this was tested in troubleshoot mode.

Version: unspecified → Thunderbird 115

This is covered by bug 1725127.

Status: UNCONFIRMED → RESOLVED
Closed: 6 months ago
Duplicate of bug: 1725127
Resolution: --- → DUPLICATE

This has still not been resolved as I see the issue in the latest Thunderbird release 115.6.1. Or it has been re-introduced. It doesn't appear to refresh the screen in troubleshoot mode so it doesn't appear to show up there. At least, not when I tried.

The original bug was reported 3 years ago. This issue re-appeared a few months ago so must have been re-introduced.
I don't have any extensions enabled. Just vanilla Thunderbird, running on Windows 11.

(In reply to Tim Beuman from comment #3)

This has still not been resolved as I see the issue in the latest Thunderbird release 115.6.1.

The fix for bug 1725127 has been in beta for 10 days now and should land in ESR 115 soon.

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