-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[$1000] Visiting room by pasting URL, doesn't read messages - reported by @K4tsuki #7837
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.
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
Comments
Triggered auto assignment to @flaviadefaria ( |
Makes sense to fix this. I also tested in Slack and after a few seconds in the room, the conversation is "marked as read" and the room name is no longer flagged in bold. |
Triggered auto assignment to @joelbettner ( |
Yeah, this should definitely be fixed. Un-assigning myself and labeling as external. |
Triggered auto assignment to @JmillsExpensify ( |
maybe duplicate of #6471 |
Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Is this duplicate issue? Could I submit a proposal? |
6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it! |
10 days overdue. Is anyone even seeing these? Hello? |
This issue has not been updated in over 14 days. eroding to Weekly issue. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry for the spammin' |
It does not look related. But we can ask QA to retest it when #6471 is on staging. |
Doubled price to $500 |
Not overdue! |
Doubled price to $1000 |
After #6471 was deployed to staging I was unable to reproduce it from my side, I think we could tag some QA and see if it's still reproducible.
I think even its not being related we ended up also solving this one in #6471 Just need to confirm with some QA |
@isabelastisser @mvtglobally can you test to see if you're able to reproduce? Thanks! |
Hey @mallenexpensify , did you mean to tag @isagoico? :) |
Indeed! Sorry @isabelastisser (I'm surprised this doesn't happen 10x as much) |
@isagoico and @mvtglobally , are you able to reproduce? |
This comment was marked as resolved.
This comment was marked as resolved.
@isagoico I think that for this issue you should open it directly by pasting the URL.
Is that right? cc: @parasharrajat |
I was unable to reproduce the same issue on my side following those steps. Please check the video and let me know if the steps are incorrect. Recording.4.mp4 |
You're right, that's the correct steps. But I think that's the expected behavior, isn't? Expected Result:Room style must be displayed as read (not in bold) and unread indicator line will disappear after user scroll chat up and down. |
Yeap, the issue is not reproducible. Behavior was the expected on my side. |
If no one can reproduce it, let's close it! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
Room style must be displayed as read (not in bold) and unread indicator line will disappear after user scroll chat up and down.
Actual Result:
Room style keep displayed as unread and unread line indicator (green line) keep being shown even after user scroll up and down in the message. Even after user navigate to other room, room style keep displayed as unread.
Workaround:
unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.39-1
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
marker.mp4
Expensify/Expensify Issue URL:
Issue reported by: @K4tsuki
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1644253704477339
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: