We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write the following message:
https://some.link1/_/lol and https://some.link2/_/bar
And send the message.
I expect to see 2 links, and zero emphasize.
I have 2 broken links, and emphasize between /lol up to link2/.
/lol
link2/
The Markdown parser considers _ as an emphasize marker, instead of being part of the URL.
_
It happens also in Element Web. Not tested on Android.
No response
iOS
nightly 1.2.1 (300)
No
The text was updated successfully, but these errors were encountered:
It seems that the formatted body is "formatted_body": "https://some.link1/<em>/lol and https://some.link2/</em>/bar" which would point to this being a Rust side bug coming from here https://github.com/matrix-org/matrix-rust-sdk/blob/main/bindings/matrix-sdk-ffi/src/timeline.rs#L50C8-L50C43
"formatted_body": "https://some.link1/<em>/lol and https://some.link2/</em>/bar"
Sorry, something went wrong.
Indeed, I ended up in Ruma, which uses pulldown_cmark. I'll raise the bug there.
pulldown_cmark
Issue raised here, pulldown-cmark/pulldown-cmark#695.
Closing this issue, as it's not a bug, it's just how CommonMarkdown is defined.
No branches or pull requests
Steps to reproduce
Write the following message:
And send the message.
Outcome
What did you expect?
I expect to see 2 links, and zero emphasize.
What happened instead?
I have 2 broken links, and emphasize between
/lol
up tolink2/
.The Markdown parser considers
_
as an emphasize marker, instead of being part of the URL.It happens also in Element Web. Not tested on Android.
Your phone model
No response
Operating system version
iOS
Application version
nightly 1.2.1 (300)
Homeserver
No response
Will you send logs?
No
The text was updated successfully, but these errors were encountered: