Skip to content

Unread indicator doesn't clear if you are in the room that a new comment is posted in #42

Description

@tgolen
No description provided.

Activity

  1. tgolen commented on Aug 11, 2020

    @tgolen
    ContributorAuthor

    this is fixed

  2. added this to the Alpha Launch milestone on Aug 12, 2020
  3. quinthar commented on Aug 12, 2020

    @quinthar
    Contributor

    Hm, I'm not totally convinced it is, I'd love to test this in production with someone to verify that it's fixed. Marking CRITICAL because we are going to be promoting this as a rock-solid solution, so reliability is key.

  4. quinthar commented on Aug 12, 2020

    @quinthar
    Contributor

    Looking for issues to demote, this doesn't seem as critical as the others, reducing to HIGH

  5. AndrewGable commented on Aug 12, 2020

    @AndrewGable
    Contributor

    I had issues with this working well this morning with a ton of unread chats

  6. tgolen commented on Aug 15, 2020

    @tgolen
    ContributorAuthor

    Huh, odd... it seems to just always work for me. Hopefully, we can find a way to reproduce it or capture what's actually happening.

  7. quinthar commented on Aug 15, 2020

    @quinthar
    Contributor

    Ya, I can't reproduce this one. This is what I tried:

    1. Open up #react-ion room in my main browser window (dbarrett@expensify.com), and incognito window (dbarrett@quinthar.com)
    2. In the main window, pick a different tab (so ChatDot isn't in the foreground)
    3. Comment in the incognito window, comment in the room
    4. I correctly see that there is an unread comment in the tab
    5. When I switch to the tab, it immediately marks the unread comment as read
    6. The LHN correctly shows there is nothing unread
  8. quinthar commented on Aug 15, 2020

    @quinthar
    Contributor

    Same steps work if the "main window" is replaced with the Android app (though Pusher still seems kinda flaky to me -- it's not 100% reliable about sending new actions to the open report, but I think that's a different issue). I'm going to close this until someone can provide reproduction steps.

  9. added a commit that references this issue on Feb 1, 2024
  10. added a commit that references this issue on Mar 30, 2026
  11. IuliiaHerets commented on Apr 1, 2026

    @IuliiaHerets

    Hi @tgolen. Do we need to QA this?

    cc @quinthar @AndrewGable

  12. AndrewGable commented on Apr 1, 2026

    @AndrewGable
    Contributor

    No, this is a super old PR and was incorrectly linked

  13. OSBotify commented on Apr 2, 2026

    @OSBotify
    Contributor

    🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.3.51-10 🚀

    platform result
    🕸 web 🕸 success ✅
    🤖 android 🤖 failure ❌
    🍎 iOS 🍎 success ✅
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions