Messages marked as read even when window is out of focus (but not minimized)

[KHerschbach]

Tip

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

---

Steps to reproduce

1. Open any conversation in Talk.
2. Open another app so that the Talk window is out of focus, but not minimized.
3. Incoming messages in the open conversation won't produce notifications (e.g. in the desktop app) and will be marked as read.

Expected behaviour

AFAIK, other messenger apps like Slack check whether the window is in focus to decide whether you're currently looking at the currently open conversation. If it is out of focus, minimized etc., they will display a notification and the message will be treated as unread until the window is back in focus. I expect Talk to handle it similarly.

Actual behaviour

If I'm working in another app and Talk is open behind it, the person in my currently open conversation can send me as many messages as they want, I won't get notified. And they might think I've read the messages already, since Talk displays the two checkmarks. When I bring Talk back into focus, I might not even notice that there are new messages, since nothing indicates that to me.

I can confirm this behaviour is the same for the Talk app on Mac.

Talk app

Talk app version: I'm not the admin, but should be v25.0.0.

Custom Signaling server configured: Same here, no admin.

Custom TURN server configured: Same here, no admin.

Custom STUN server configured: Same here, no admin.

Browser

Microphone available: yes

Camera available: yes

Operating system: Mac

Browser name: Firefox

Browser version: 156.0.1 (aarch64)

[Antreesy]

Should be fixed with #19097

Please check which version you're on - Navigation > App settings > scroll down to see it

[KHerschbach]

@Antreesy

I'm on Talk web version 25.0.1 and on macOS client version 2.3.2. Just tested it again and the problem persists.

[Antreesy]

There's a grace period of 60 seconds after window blurred, after which browser console (also desktop app console) logs:

• console.info('Session has been marked as inactive')
• server starts sending notifications for this room (if they are enabled)
• client stops sending /read requests for new messages

Last time I tested this PR, it was behaving as expected. If you can confirm seeing this in your console, and your client still sends /read requests, then something's off