Prepend message type in thread panel

[daniellekirkwood]

Your use case

What would you like to do?

In the Thread list panel there's no details about the type of message that the thread root is. This is quite confusing.

The first message in this list is a poll and the third is a sticker.

Why would you like to do it?

Make the product better

How would you like to achieve it?

Prepend the event with the event type where the rendering has to change

eg:

We do this in the room list for message previews and now with pinned messages

Have you considered any alternatives?

No response

Additional context

No response

[t3chguy]

We do this in the room list for message previews

I can't reproduce that

Do designs for this exist wrt font and all the available copy options for the many types of event?

[daniellekirkwood]

[daniellekirkwood]

@americanrefugee would you be able to mock up a screen or two of what i'm describing here? Do you agree that it's a direction we'd want to go?

[daniellekirkwood]

The link to the document we started making notes in is here: https://www.figma.com/design/gpxHFDTNK796n84r1ZxYG2/Room-Header-%26-Details-(2024)?node-id=1320-62268&node-type=canvas&t=p2yAj4jSdyZwFDor-0

[daniellekirkwood]

@t3chguy I would like to make it clearer to users the type of message that appears in the right panel (if it's not immediately obvious). This could also apply to the room list too (right now we have an icon for a thread message but nothing else).

In the pinned message banner, we do prepend the message with the type where type != message.

Would you help me by describing what someone might need in order to make this issue ready to be worked on? I can then pull that info together in the description.

(tagging you because it's currently part of the room header & right panel work) :)

EG:

[t3chguy]

If it already exists for Pinned messages then we can probably just say to copy that

[t3chguy]

@daniellekirkwood do we want the same prefix for thread replies too?

e.g. if Testing was the name of a file should it be *File*: Testing

[daniellekirkwood]

I think that might be overkill but yes, let's lean into it and see if there's any responses? I'd rather be clear than confusing... especially given the number of accessibility reports we get about confusing content... 😂