You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Send in a room mention and a user mention with tab-completion. The resulting JSON body will include the following field:
"formatted_body": "Hello <a href=\"https://matrix.to/#/@phishbot:matrix.org\">@Phish Bot</a> come join <a href=\"https://matrix.to/#/#gemiweb0:matrix.org\">#gemiweb0, the HTML subset</a>",
Expected behavior
The resulting JSON body should include the following field:
"formatted_body": "Hello <a href=\"https://matrix.to/#/@phishbot:matrix.org\">Phish Bot</a> come join <a href=\"https://matrix.to/#/#gemiweb0:matrix.org\">#gemiweb0:matrix.org</a>",
Platform and versions
Cinny Web v4.2.3
Additional context
No response
The text was updated successfully, but these errors were encountered:
You are right. I have now updated the description. Note that neither the example JSON, nor the text implies that an @ sign should be included, so Cinny is still in error in both cases.
bkil
changed the title
Pill user and room mention anchor text should contain mxid, not display name
Anchor text of user pill should contain only display name and room mention the room alias or ID
Nov 25, 2024
Describe the bug
Generated
formatted_body
in JSON is not compliant with the specification:Reproduction
Send in a room mention and a user mention with tab-completion. The resulting JSON body will include the following field:
"formatted_body": "Hello <a href=\"https://matrix.to/#/@phishbot:matrix.org\">@Phish Bot</a> come join <a href=\"https://matrix.to/#/#gemiweb0:matrix.org\">#gemiweb0, the HTML subset</a>",
Expected behavior
The resulting JSON body should include the following field:
"formatted_body": "Hello <a href=\"https://matrix.to/#/@phishbot:matrix.org\">Phish Bot</a> come join <a href=\"https://matrix.to/#/#gemiweb0:matrix.org\">#gemiweb0:matrix.org</a>",
Platform and versions
Additional context
No response
The text was updated successfully, but these errors were encountered: