Closed
Bug 1924728
Opened 10 days ago
Closed 4 days ago
Disabling "Grouped by Sort" while a group header is selected may break the message pane
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(thunderbird_esr128 unaffected, thunderbird131 affected, thunderbird132 affected)
RESOLVED
FIXED
133 Branch
Tracking | Status | |
---|---|---|
thunderbird_esr128 | --- | unaffected |
thunderbird131 | --- | affected |
thunderbird132 | --- | affected |
People
(Reporter: welpy-cw, Assigned: welpy-cw)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Steps to reproduce:
- Select a folder that is grouped by sort, all groups collapsed.
- Select a group header.
- Change to threaded or unthreaded view.
Actual result:
The message pane doesn't work properly any more, the console shows
Uncaught : Component returned failure code: 0x80550018 [nsIMsgDBView.getURIForViewIndex]
saveSelection chrome://messenger/content/about3Pane.js:5060
onDestroyingView chrome://messenger/content/mailCommon.js:1033
_applyViewChanges resource:///modules/DBViewWrapper.sys.mjs:1530
set _viewFlags resource:///modules/DBViewWrapper.sys.mjs:1498
set showThreaded resource:///modules/DBViewWrapper.sys.mjs:1891
toggleThreaded chrome://messenger/content/about3Pane.js:6708
init chrome://messenger/content/about3Pane.js:4352
setColumn chrome://messenger/content/tree-view.mjs:2437
about3Pane.js:5060
Assignee | ||
Comment 1•10 days ago
|
||
Updated•10 days ago
|
Assignee: nobody → h.w.forms
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•10 days ago
|
||
Actually, this doesn't work quite right in 115 and 128 either, because in the case of the STR, the first message of a group is selected after changing the view. But the message pane remains functional.
Assignee | ||
Comment 3•5 days ago
|
||
Keywords: checkin-needed-tb
Target Milestone: --- → 133 Branch
Pushed by brendan@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/9c9bc29de367
Make isGroupedByHeaderAtIndex work properly when the view is already closed. r=mkmelin
You need to log in
before you can comment on or make changes to this bug.
Description
•