Skip to content
This repository has been archived by the owner on Oct 17, 2019. It is now read-only.

Unknown message types are not displayed #143

Open
Ralith opened this issue Nov 30, 2017 · 2 comments
Open

Unknown message types are not displayed #143

Ralith opened this issue Nov 30, 2017 · 2 comments

Comments

@Ralith
Copy link
Contributor

Ralith commented Nov 30, 2017

Per the m.room.message spec, the "body" key of message event content

MUST be used with every kind of msgtype as a fallback mechanism for when a client cannot render a message.

Nheko thus can and should display the contents of this key to the user as plain text for unrecognized messages.

@mujx
Copy link
Owner

mujx commented Nov 30, 2017

Just to keep track of the missing messages

  • m.video
  • m.audo
  • m.location

@Ralith
Copy link
Contributor Author

Ralith commented Dec 1, 2017

To be clear, this is not a problem of missing handling for specific message types. This is a problem of missing handling for otherwise unhandled message types, and is needed regardless of what message types are handled.

@mujx mujx added this to the v0.5.0 milestone May 2, 2018
@mujx mujx removed this from the v0.5.0 milestone Jun 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants