Element-web: Grey shields should mean "encrypted but of unknown trust" rather than unencrypted(!)

[ara4n]

The fact that this is an unencrypted message popping up in an encrypted room (in this instance because it precedes encryption being enabled) feels a bit weird - there's something solidly reassuring about a black shield, whereas in practice this msg wasn't encrypted at all!

[nadonomy]

Design proposal with rationale detailed in Figma here: https://www.figma.com/file/wwqBo5oAFfk8XKmtd2YaIs/Cross-signing?node-id=0%3A1

[uhoreg]

@nadonomy is there a different design for events that are expected to be unencrypted (such as joins), or should they look like all the other unencrypted events?

[nadonomy]

@uhoreg ah good question. I think the most sensible thing to do is to not decorate them with warnings either, with the rationale being:

(a) Users don't care or shouldn't have to care about the distinction between messages and events— the mental model needed for them to make sense of any encryption decoration seems like a net loss
(b) We can ensure the app & decoration is correct by ensuring micro copy refers to messages being encrypted, rather than events or rooms

[turt2live]

I think this is the section @nadonomy is referencing? (the figma is a bit large)