UX idea: unread messages marker when losing focus #44

Closed
opened 2026-10-05 01:54:51 +02:00 by adam · 3 comments
Owner

Say I'm focused on "Public" channel, and then leave browser focus (or screensaver, or phone goes to sleep, or etc).

When I come back to focus, should there be an "unread messages" marker at the point I stopped paying attention? Is it even possible?

Say I'm focused on "Public" channel, and then leave browser focus (or screensaver, or phone goes to sleep, or etc). When I come back to focus, should there be an "unread messages" marker at the point I stopped paying attention? Is it even possible? <!-- github-sync-id:4091393300 -->
adam closed this issue 2026-10-05 01:54:51 +02:00
Author
Owner

Mmmm, good question. Absolutely technically feasible, but there would be question marks around whether we should increment only when the window is completely invisible, or anytime it's unfocused, like if it's just open on another monitor but not being clicked inside of.

I'm inclined to say that any focused conversation should be considered read without trying to get too fancy about the user's browser window state, but I get where you're coming from. I don't know that there's a situation that I love with all my heart, including how I currently have it.

Mmmm, good question. Absolutely technically feasible, but there would be question marks around whether we should increment only when the window is completely invisible, or anytime it's unfocused, like if it's just open on another monitor but not being clicked inside of. I'm inclined to say that any focused conversation should be considered read without trying to get too fancy about the user's browser window state, but I get where you're coming from. I don't know that there's a situation that I love with all my heart, including how I currently have it. <!-- github-comment-id:4078231782 -->
Author
Owner

Perfectly happy if you table this. It does need planning out how the behaviors all inter-relate cohesively.

Perfectly happy if you table this. It does need planning out how the behaviors all inter-relate cohesively. <!-- github-comment-id:4078289140 -->
Author
Owner

I think I'm gonna close this for now. I'm happy with how our unreads track and am going to keep it as is unless I get some more critical pushback.

I think I'm gonna close this for now. I'm happy with how our unreads track and am going to keep it as is unless I get some more critical pushback. <!-- github-comment-id:4119924200 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#44