Skip to content

Show edited/moved marker on messages #171

Closed
@gnprice

Description

@gnprice

When a message has been edited or moved, Zulip web shows this with a small "EDITED" or "MOVED" marker. This can be important for understanding a conversation; we should do either the same thing or another way of conveying the same information.

The Help Center describes this feature on the following page:
https://zulip.com/help/view-a-messages-edit-history
though that page also covers showing the details of the edits or moves, which is a separate issue #531.

UI design

See first comments below, and see this later chat thread:
https://chat.zulip.org/#narrow/stream/48-mobile/topic/check-x.20icons.20in.20left.20margin/near/1908288

Implementation

We don't currently store the information of whether and how a message has been edited or moved. The first phase of work on this issue will be to start storing and maintaining that information. This will involve adding a field to the Message class, and then updating that field as appropriate in response to events.

Concretely, this field should look like MessageEditState edited; where MessageEditState is an enum with three values: none, moved, and edited. In other words it will store only the information needed to control the edited/moved marker; storing the full edit history is out of scope for this issue (and will be left for #531).

After that we can start showing the information in the UI.

Related issues

These related features are all out of scope for this issue:

(The details of the edits or moves can be important information too, but for a lot of purposes just the fact that the message was edited or moved, or the ability to confirm that it wasn't, is very helpful.)

Note that some of these have the "Post-launch" milestone — those are things we expect to get to much later than this issue.

Metadata

Metadata

Assignees

Labels

a-msglistThe message-list screen, except what's label:a-content

Type

No type

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions