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
This is a follow-up to #844, and its fix #1086. The added @mention works well, but for some reason a paragraph is added around the mention, breaking the mention into its own line.
ActivityPub representation including the line break: https://herve.bzh/?c=173&activitypub <p><a class="u-mention mention" href="https://mastodon.social/@inkican">@[email protected]</a></p><p>I’ll add it to my « To read » list, thank you! 🙂</p>
Steps to reproduce
Publish a post
Have another comment reply to the post on the Fediverse
On your site, reply to the comment via Federation
View the reply in the Fediverse client
What you expected to happen
I would expect the reply to include a @mention of the person I'm replying to, immediately followed by my reply.
What actually happened
Instead the @mention is followed by a line break.
Impact
All
Available workarounds?
There is no user impact
Logs or notes
No response
The text was updated successfully, but these errors were encountered:
This issue could use some more labels, to help prioritize and categorize our work. Could you please add at least a [Type], a [Feature], and a [Pri] label?
Quick summary
This is a follow-up to #844, and its fix #1086. The added @mention works well, but for some reason a paragraph is added around the mention, breaking the mention into its own line.
Here is an example:
<p><a class="u-mention mention" href="https://mastodon.social/@inkican">@[email protected]</a></p><p>I’ll add it to my « To read » list, thank you! 🙂</p>
Steps to reproduce
What you expected to happen
I would expect the reply to include a @mention of the person I'm replying to, immediately followed by my reply.
What actually happened
Instead the @mention is followed by a line break.
Impact
All
Available workarounds?
There is no user impact
Logs or notes
No response
The text was updated successfully, but these errors were encountered: