don't outline and track muted comments#2846
Conversation
|
Currently that indicator is very, very light. It only reads Batch-checking live comments on 21 items (homepage) can be expensive and as you said, we'd have to nail down the performance. I wonder if we can come up with a slim query that just gets We'd probably need to rethink how we manage new comments in general. |
|
I've tested the in-item functionality and this worked as I expected. One minor question: when you say "tracking with the navigator", you mean that the blue dot at the top bar (when in item view) only tracks non-muted replies too? Is that a correct understanding? Because that's what I noticed - if yes, then I'll test that a bit deeper. |
|
Yes exactly, the new comments navigator tracks new outlined comments. By not outlining the new muted comments, we're also not tracking them. |
|
Tested that part with mutes, without mutes and all that looks fine. I did notice that when a new comment is hidden behind pagination (note: unlikely with current parametrization |

Description
#2842
Checks if the author of the new comment is not muted before outlining it (and tracking it via navigator).
Screenshots
Screen.Recording.2026-03-08.at.14.39.07.mov
Additional Context
Maybe muted comments should appear at the bottom rather than the top!
Checklist
On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:
10
Note
Low Risk
Small UI/UX logic change gated by a mute flag; minimal blast radius and no security or data-handling impact.
Overview
Prevents muted users’ comments from being treated as “new” on item pages.
Commentnow bails out of the outlining/navigator.trackNewCommenteffect whenitem.user.meMuteis set, so muted comments won’t be highlighted or counted in the new-comment navigator flow.Written by Cursor Bugbot for commit 3d0098a. This will update automatically on new commits. Configure here.