mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-03-26 13:04:10 +01:00
Clients cannot ignore edits
This commit is contained in:
parent
97b7544f2c
commit
05d1779d1f
|
|
@ -259,17 +259,9 @@ difficult, and servers should no longer make this replacement.
|
||||||
|
|
||||||
#### Client behaviour
|
#### Client behaviour
|
||||||
|
|
||||||
Clients can often ignore `m.replace` events, because any events returned
|
Since the server will not replace the content of any edited events, clients
|
||||||
by the server to the client will be updated by the server to account for
|
should take note of any replacement events they receive, and apply the
|
||||||
subsequent edits.
|
replacement whenever possible and appropriate.
|
||||||
|
|
||||||
However, clients should apply the replacement themselves when the server is
|
|
||||||
unable to do so. This happens in the following situations:
|
|
||||||
|
|
||||||
* The client has already received and stored the original event before the
|
|
||||||
message edit event arrives.
|
|
||||||
|
|
||||||
* The original event (and hence its replacement) are encrypted.
|
|
||||||
|
|
||||||
Client authors are reminded to take note of the requirements for [Validity of
|
Client authors are reminded to take note of the requirements for [Validity of
|
||||||
replacement events](#validity-of-replacement-events), and to ignore any
|
replacement events](#validity-of-replacement-events), and to ignore any
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue