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
When the thread preview is rendered in the timeline, it removes all the formatting, and this can be misleading when the last message contains quote.
For instance here:
benoit did not really write This message is sent by another user, but just quoted it.
benoit
This message is sent by another user
With the example the consequences are not important, but it can be really bad with other messages, I let you imagine what it could be.
So I would like the thread preview in the main timeline to be reliable regarding who has said what.
Trust in the product, and avoid confusion.
Remove quoted content to render the thread preview, or any other solution.
No response
The text was updated successfully, but these errors were encountered:
Duplicate of #19945
Sorry, something went wrong.
No branches or pull requests
Your use case
What would you like to do?
When the thread preview is rendered in the timeline, it removes all the formatting, and this can be misleading when the last message contains quote.
For instance here:
benoit
did not really writeThis message is sent by another user
, but just quoted it.With the example the consequences are not important, but it can be really bad with other messages, I let you imagine what it could be.
So I would like the thread preview in the main timeline to be reliable regarding who has said what.
Why would you like to do it?
Trust in the product, and avoid confusion.
How would you like to achieve it?
Remove quoted content to render the thread preview, or any other solution.
Have you considered any alternatives?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: