Thread summary ignores text decorations

[HarHarLinks]

Steps to reproduce

Outcome

What did you expect?

not everything is needed, but decorations like strikethrough change the meaning and should be reflected

What happened instead?

Looks to me like it's filtered similarly or the same way previews in the room list are. Some stuff gets HTML-escaped, e.g. < > but if it actually reuses the room list preview code then that has been fixed on develop.



Reactions aren't shown at all, but I don't know what I expect there.

Operating system

w10

Application version

Element version: 1.9.5 Olm version: 3.2.3

How did you install the app?

element.io

Homeserver

No response

Will you send logs?

No

[daniellekirkwood]

thanks for raising this issue!

@janogarcia Should the Thread Summary have the same treatment as message previews in the left panel, or should we be striving for a different solution here? Previews in the Room list view do not show text decorations, but they do show reactions.

[HarHarLinks]

Previews in the Room list view do not show text decorations

However, both room list and thread summary should respect certain decorations, like hiding spoilers or strike through. What I mean to say is that it's possibly okay to reuse the same "preview code", but it needs a bit of polish for such features whichever way it is done. The same rules also apply to notifications, by the way.

but they do show reactions.

Isn't this a labs feature?

Still I agree with the notion that it needs to be decided how to handle them.

[t3chguy]

Related #16330

[germain-gg]

This issue about room list previews is tracked as part of #19615

[janogarcia]

I'd just add that, as a first step, I documented the inconsistencies for "rendering content types and formatting styles" across all platforms. Also, opened issues for each platform to somehow address the inconsistencies.

For this first iteration we have taken the current implementation for Web as the reference implementation. The next step will be figuring out how to improve that spec, and make it more usable, which includes revisiting how we render those content types and formatting styles (such as those mentioned by HarHarLinks) in those contexts.

[HarHarLinks]

revisiting how we render those content types and formatting styles

I don't have a link, but there has been talk about the idea to outsource the markdown compiler to a common custom rust library, which would possibly also integrate here

[quazgar]

This bug affecting spoiler blurring will become more urgent as thread responses are enabled by more and more users.

Bug reproduced in:
Element version: 1.11.0
Olm version: 3.2.8