You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Email of users in the message rection list (which is opened by long-press on an existing reaction or by clicking on "See who reacted" from message action sheet) should be hidden when the original email is not visible to the user according to the email_address_visibility settings of the organization.
There is no use of showing the emails generated by user-id (of the form user1888@example.com), as it does not provide any information about the user.
The text was updated successfully, but these errors were encountered:
In fact I think the best thing to do is to go farther than that: we should just leave out the email addresses on this screen unconditionally. Even when real email addresses are available, in this context they feel mostly like clutter.
The code that implements this screen is in src/reactions/MessageReactionList.js.
Removes user emails from the user list in the message reactions
screen because in this context, the emails mostly feel like
clutter.
As a side effect of this change, we no longer have to worry about
the server 'email_address_visibility' setting.
Fixes: zulip#4188.
Removes user emails from the user list in the message reactions
screen because in this context, the emails mostly feel like
clutter.
As a side effect of this change, we no longer have to worry about
the server 'email_address_visibility' setting for this screen.
Fixes: zulip#4188.
Email of users in the message rection list (which is opened by long-press on an existing reaction or by clicking on "See who reacted" from message action sheet) should be hidden when the original email is not visible to the user according to the email_address_visibility settings of the organization.
There is no use of showing the emails generated by user-id (of the form user1888@example.com), as it does not provide any information about the user.
The text was updated successfully, but these errors were encountered: