Skip to content

NEXUS-4328: Keep selected messages unread across navigation #3026

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
kazemek21 wants to merge 1 commit into from
Closed

NEXUS-4328: Keep selected messages unread across navigation #3026

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions docs/buzz-help.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -394,8 +394,12 @@ revokes all of them, and a pairing unused for 30 days expires.
read: unread threads keep their dots in the conversation and in Activity →
Threads, and **New messages** still marks where you left off. A mention, DM or
reply to you that arrives after you leave lights the row again, as does any
newer message; **Mark as unread** still shows on it. On another device, rows
with unread mentions, DMs or replies to you light again until you read them.
newer message; **Mark as unread** still shows on it. The channel message
menu's **Mark unread** keeps the selected message and currently loaded reply
subtree unread when you leave and reopen that channel during this window
session. Reading the selected subtree or channel in that window clears the exact mark. It is
not restored after Buzz restarts. On another device, rows with unread
mentions, DMs or replies to you light again until you read them.
- **Communities** have their own channels, people, and agents. Switch with
the community switcher at the bottom of the dock; in **Personal space**,
Messages offers **Choose a community**, which opens it. Switching
Expand Down
9 changes: 9 additions & 0 deletions docs/unread.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,6 +103,15 @@ viewport):
marked unread keep their intent. These marks stay on this device:
frontier-only sync never publishes `msg:` marks, though it still reads them
from older clients.
- The channel message menu's **Mark unread** keeps the selected message and its
currently loaded reply subtree as exact unread targets for the current window
session. Leaving and reopening the channel does not clear those IDs: shared
message selectors continue to report them after the sidebar hint is
reconciled. Explicit reads clear only the selected targets their scope and
frontier cover, even after observation eviction; a DM thread read preserves
selections in other threads. Deletion, access retirement, and session disposal
end the intent. The exact target set is not restored as a restart-persistent
mark.
- `thread-activity:<root>` acknowledges replies through the newest reply only in
that thread. A collapsed newest reply, or one outside the bottom viewport in a
branch-ordered thread, cannot earn catch-up; visible rows still read individually.
Expand Down
Loading
Loading