Skip to content
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

timestamp is hidden by the avatars on emotes #2284

Open
richvdh opened this issue Sep 19, 2016 · 11 comments
Open

timestamp is hidden by the avatars on emotes #2284

richvdh opened this issue Sep 19, 2016 · 11 comments
Labels
A-Emotes A-Timeline O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Tolerable Low/no impact on users T-Defect X-Needs-Design

Comments

@richvdh
Copy link
Member

richvdh commented Sep 19, 2016


  • emote
  • /me, me slash command
  • status message
@ara4n
Copy link
Member

ara4n commented Oct 10, 2016

This is because I broke the official emote design in order to make it clearer who emotes are attributed to. @antikewl, we'll need to reconsider how to show emotes - I think we need a big avatar in order to make it easier to see who is emoting about what, given they are just as important and personal as normal messages. But the big avatar overlaps the timestamp and hides it.

@ara4n ara4n changed the title timestamp is invisible on emotes timestamp is hidden by the avatars on emotes Oct 10, 2016
@ara4n ara4n added T-Defect P2 S-Tolerable Low/no impact on users design labels Oct 10, 2016
@mittalswastik
Copy link

What I understand by @ara4n's comment is that we are trying to accomplish adding reactions to messages sent by the user. Questions are as follows:

  • Does emote over here refers to emoticons?
  • If the above question's answer is yes: where exactly can I embed emoji's? Can't find a toolbar for emoji's and I tried following the conventional UX of typing :) -> to turn into emoji. Nothing happened.

Can you elaborate the issue a little, so I can take this up?

@richvdh
Copy link
Member Author

richvdh commented Apr 12, 2017

@mittalswastik: I think you're over-reading this. 'emote' refers to /me messages. Reactions are covered at #1357.

@turt2live
Copy link
Member

This is slightly more amusing when you enable 12hr time:
image
(/develop)

@Angedestenebres
Copy link
Contributor

Hi again,

Sorry @ara4n I didn't find that issue :S
Anyway thanks for your prompt answer.

After checking I find a way to display the exact timestamp on Desktop Client:

screenshot_2018-05-17_14-45-22

For that, we just have to place the cursor near of the user's avatar to get the mouseover :)

@t3chguy
Copy link
Member

t3chguy commented Jul 11, 2018

Is this dealt with in the redesign?
One option would be to set opacity on the avatar on hover
like
image

@turt2live
Copy link
Member

More irritatingly, when the emote is in a reply the timestamp is on top of the avatar where normally it is underneath:
image

@nadonomy
Copy link
Contributor

Updating with a screenshot of what Riot (/develop) looks like today:

Screenshot 2019-05-31 at 13 22 48

We could consider moving the timestamp next to the name, and displaying the name on emotes.

@ara4n
Copy link
Member

ara4n commented Jul 7, 2021

Screenshot 2021-07-07 at 14 53 36

the current misbehaviour just looks awful.

@kittykat kittykat added the O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience label Sep 14, 2021
@Johennes
Copy link
Contributor

An alternative could be to use the regular two-line layout for emotes as well, e.g.

[Avatar]   Kegan
 14:52     * fiddles

@HarHarLinks
Copy link
Contributor

This has recently gotten worse as Compound for some reason made flabback/placeholder avatars half transparent:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Emotes A-Timeline O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Tolerable Low/no impact on users T-Defect X-Needs-Design
Projects
None yet
Development

Successfully merging a pull request may close this issue.