-
Notifications
You must be signed in to change notification settings - Fork 499
New issue
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
Room decoration: shields #2906
Labels
feature
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements
Milestone
Comments
This was referenced Jan 15, 2020
manuroe
added this to the Sprint 25: Cross-signing and e2e by default - phase 1 milestone
Jan 17, 2020
Kamino cloned this issue to vector-im/riot-ios |
Because of room members lazy loading, we may not have enough data to compute the right shield to display for a room. In this case, use the black shield. |
manuroe
added a commit
to matrix-org/matrix-ios-sdk
that referenced
this issue
Jan 31, 2020
…s and devices in the room element-hq/element-ios/issues/2906)
manuroe
added a commit
that referenced
this issue
Jan 31, 2020
kittykat
added
the
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements
label
Apr 6, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feature
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements
From riot-web created by dbkr: element-hq/element-web#11225
Legend in figma around: https://www.figma.com/file/wwqBo5oAFfk8XKmtd2YaIs/Cross-signing?node-id=2363:11
Decorate rooms with black/green/red shields as appropriate.
This decoration should only appear when the cross-signing labs flag is enabled.
(The following describes rooms in terms of users, but updating the shields on users in the UI is left to a separate issue #2905.)
For some additional detail, the shields are meant to layer onto the room icon in both the room list and room header:
The text was updated successfully, but these errors were encountered: