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

Impossible to hover cursor on the edit mark icon of the messages next to the first #24962

Closed
Kyogre opened this issue Mar 26, 2022 · 5 comments
Closed
Labels

Comments

@Kyogre
Copy link

Kyogre commented Mar 26, 2022

Description:

It is impossible to hover cursor on the pencil icon of the edited messages, underneath the first message.

Steps to reproduce:

  1. User send 2 (or more) message in a row.
  2. Somebody (same user or moderator) edits the second message.
  3. User tries to hover cursor on the pencil icon, but the icon disappears.

Expected behavior:

User can hover cursor on the edit mark icon of the second (and next) message.

Actual behavior:

User can't see who and when edited any of his messages. On the subsequent messages, grouped, there is no way of showing the edit mark icon.
Video demo: https://user-images.githubusercontent.com/2260980/160235618-66b32e60-f17c-4d9d-96b7-351187b409f2.mp4

Server Setup Information:

Tried on https://open.rocket.chat/

Additional context

Discussed here: https://forums.rocket.chat/t/impossible-to-hover-cursor-on-the-edit-mark-icon-of-the-messages-next-to-first/13664

@aakash-gitdev
Copy link
Contributor

Hey I am still trying to understand the codebase. Can you help me out with finding the relevant code directory for this issue? Will be a great help! I want to work on this issue.

@Dnouv
Copy link
Member

Dnouv commented May 5, 2022

Hello @aakash-gitdev
Are you still working on this issue? Just confirming, if you are, then please let me know.
Thank you!

@aakash-gitdev
Copy link
Contributor

Right now my university examinations are going on. But after they get over I will continue with this.

@Kyogre
Copy link
Author

Kyogre commented May 6, 2022

I haven't tested it yet, but maybe it is fixed in #24984 ?

@dudanogueira
Copy link
Contributor

Indeed. This was fixed in latest 4.8.0 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants