Closed Bug 1921618 Opened 2 months ago Closed 1 month ago

Switching from "Threads/Unread" to "Threads/Threads with Unread" has no apparent effect

Categories

(Thunderbird :: Folder and Message Lists, defect)

Thunderbird 128
defect

Tracking

(thunderbird_esr115 wontfix, thunderbird_esr128? affected, thunderbird132 affected, thunderbird133 verified)

VERIFIED FIXED
133 Branch
Tracking Status
thunderbird_esr115 --- wontfix
thunderbird_esr128 ? affected
thunderbird132 --- affected
thunderbird133 --- verified

People

(Reporter: francesco, Assigned: welpy-cw)

References

Details

Attachments

(1 file)

Switching between "All" threads, "Unread" threads and "Threads with unread" doesn't work. The behaviour appears to be somewhat random. Switching from "All" to "Unread" results in an empty message pane with this console error:

An error occurred executing the cmd_viewUnreadMsgs command: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIMsgDBView.open]"  nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame :: resource:///modules/DBViewWrapper.sys.mjs :: _createView :: line 1226"  data: no]

Subsequently switching to something else also doesn't work:

An error occurred executing the cmd_viewThreadsWithUnread command: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIMsgDBView.open]"  nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame :: resource:///modules/DBViewWrapper.sys.mjs :: _createView :: line 1226"  data: no]

The logging is from 131.0b6, but 128 is also broken.

It already doesn't appear to work correctly in 115, but I haven't investigated this in detail.

UPDATE: 115 doesn't give a console error, but switching from "Unread" to "Threads with Unread" doesn't change the view, it still only shows "Unread", one has to go "Unread" -> "All" -> "Threads with Unread" to get the desired view.

(In reply to Francesco from comment #0)

Switching between "All" threads, "Unread" threads and "Threads with unread" doesn't work. The behaviour appears to be somewhat random. Switching from "All" to "Unread" results in an empty message pane with this console error:

An error occurred executing the cmd_viewUnreadMsgs command: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIMsgDBView.open]"  nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame :: resource:///modules/DBViewWrapper.sys.mjs :: _createView :: line 1226"  data: no]

Subsequently switching to something else also doesn't work:

An error occurred executing the cmd_viewThreadsWithUnread command: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIMsgDBView.open]"  nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame :: resource:///modules/DBViewWrapper.sys.mjs :: _createView :: line 1226"  data: no]

The logging is from 131.0b6, but 128 is also broken.

It already doesn't appear to work correctly in 115, but I haven't investigated this in detail.

This seems to be another instance of the seemingly erratic behavior described in bug 1743264 which should go away as soon the affected folder has been repaired. If that's not the case, that bug could be reopened for this.

UPDATE: 115 doesn't give a console error, but switching from "Unread" to "Threads with Unread" doesn't change the view, it still only shows "Unread", one has to go "Unread" -> "All" -> "Threads with Unread" to get the desired view.

This I can confirm is bug, I am changing the summary accordingly.

Severity: -- → S4
Summary: View > Threads > Unread doesn't work → Switching from "Threads/Unread" to "Threads/Threads with Unread" has no apparent effect
See Also: → 1743264
Assignee: nobody → h.w.forms
Status: NEW → ASSIGNED

Maybe also worth fixing in the long run: Bug 321739.

See Also: → 321739
Target Milestone: --- → 133 Branch

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/f1851cdea5a5
Clear kUnreadOnly flag when switching to a special view. r=mkmelin

Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED

Confirming this issue as verified fixed with 133.0b3(20241107210012) using Windows 11, macOS 14, and Ubuntu 22.

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: