-
Notifications
You must be signed in to change notification settings - Fork 306
Mark-unread can fail if topic was concurrently moved #1045
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
Labels
a-msglist
The message-list screen, except what's label:a-content
Milestone
Comments
gnprice
added a commit
to gnprice/zulip-flutter
that referenced
this issue
Nov 5, 2024
…sheet opened The narrow of a given MessageListPage can change over time, in particular if viewing a topic that gets moved. If it does, the mark-unread action should follow along. Otherwise we'd have a frustrating race where mark-unread just didn't work if, for example, someone happened to resolve the topic while you were in the middle of trying to mark as unread. Fixes: zulip#1045
PIG208
pushed a commit
to PIG208/zulip-flutter
that referenced
this issue
Nov 7, 2024
…sheet opened The narrow of a given MessageListPage can change over time, in particular if viewing a topic that gets moved. If it does, the mark-unread action should follow along. Otherwise we'd have a frustrating race where mark-unread just didn't work if, for example, someone happened to resolve the topic while you were in the middle of trying to mark as unread. Fixes: zulip#1045
gnprice
added a commit
to gnprice/zulip-flutter
that referenced
this issue
Nov 7, 2024
…sheet opened The narrow of a given MessageListPage can change over time, in particular if viewing a topic that gets moved. If it does, the mark-unread action should follow along. Otherwise we'd have a frustrating race where mark-unread just didn't work if, for example, someone happened to resolve the topic while you were in the middle of trying to mark as unread. Fixes: zulip#1045
gnprice
added a commit
to gnprice/zulip-flutter
that referenced
this issue
Nov 7, 2024
…sheet opened The narrow of a given MessageListPage can change over time, in particular if viewing a topic that gets moved. If it does, the mark-unread action should follow along. Otherwise we'd have a frustrating race where mark-unread just didn't work if, for example, someone happened to resolve the topic while you were in the middle of trying to mark as unread. Fixes: zulip#1045
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Scenario:
Expected behavior: The message and the subsequent conversation still get marked as unread.
Actual behavior: Nothing happens. (Concretely, the app sends a mark-as-unread request aimed at the old narrow. Typically there will be no matching messages and so nothing will happen.)
I discovered this bug in the course of making other changes to the action-sheet code. #1044 contains a fix.
The text was updated successfully, but these errors were encountered: