-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Closed as not planned
Closed as not planned
Copy link
Labels
T-DefectX-Needs-InfoThis issue is blocked awaiting information from the reporterThis issue is blocked awaiting information from the reporter
Description
Steps to reproduce
The Matrix spec now uses "m.thread" as the namespaced relationship type. This has been implemented in Element Android and iOS, but the web and desktop versions still use "io.element.thread" to represent it, leading to two issues:
Thread messages sent from mobile devices cannot be processed as threads in the web and desktop applications, and vice versa.
Thread messages sent from the web or desktop applications are sometimes not visible on mobile devices, which is troublesome.
This is a thread message I sent from my PC:
"content": {
"body": "OK",
"m.mentions": {},
"m.relates_to": {
"event_id": "$xxxxxxxxx-7AyZbJENa8",
"is_falling_back": true,
"m.in_reply_to": {
"event_id": "$xxxxxxxxx-7AyZbJENa8"
},
"rel_type": "io.element.thread"
},
"msgtype": "m.text"
}
This is a thread message I sent from my phone:
"content": {
"body": "Hello, this is a message in the thread!",
"format": "org.matrix.custom.html",
"formatted_body": "Hello, this is a message in the thread!",
"m.relates_to": {
"event_id": "$xxxxxxxxxbHujOkKz3Cn5_Q1qMwc",
"is_falling_back": true,
"m.in_reply_to": {
"event_id": "$xxxxxxxxxOkKz3Cn5_Q1qMwc"
},
"rel_type": "m.thread"
},
"msgtype": "m.text"
}
They are not compatible.
Outcome
Hope that Element Web and the desktop version also implement "rel_type": "m.thread"
Operating system
windows
Browser information
edge
URL for webapp
No response
Application version
v1.11.64
Homeserver
No response
Will you send logs?
Yes
Metadata
Metadata
Assignees
Labels
T-DefectX-Needs-InfoThis issue is blocked awaiting information from the reporterThis issue is blocked awaiting information from the reporter