FAQ: Add entry discussing when messages are marked as read. #789
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
While this should normally be fairly straightforward to understand (selected/sent), this also explicitly mentions deviation (visible end of messages) and similarity (search narrows) in behavior from/with other front-ends, and the new explore mode added in e4af01e.
preetmishra
approved these changes
Aug 29, 2020
There was a problem hiding this comment.
@neiljp Thanks for working on this. This helps in explicating how we currently handle reading messages thoroughly.
Definitely a valuable addition. 👍
|
@preetmishra Thanks for the feedback 👍 This is a straightforward documentation change so I'm going to merge this now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a slightly more detailed follow-up after #787, discussing how ZT handles marking messages read, since it varies slightly from the webapp.
This was motivated after reading threads of people asking about this in the webapp, and of course we handle it differently - so we should document this!