RocketChat / Rocket.Chat

The communications platform that puts data protection first.
https://rocket.chat/
Other
40.5k stars 10.55k forks source link

Quoted message is not linked/showing with the actual parent message #19111

Open yasirrose opened 4 years ago

yasirrose commented 4 years ago

Description: Clicking on quoted message doesn't scroll to the actual message

Steps to reproduce:

  1. Open any chat
  2. Scroll up a few pages to test auto-scroll
  3. Quote any message. Type some text and hit enter.
  4. Now in the quoted message, click on the timestamp.

92946194-bf860500-f46f-11ea-85bf-9198a96614dc

Expected behavior: It should auto-scroll to the actual message that you quoted.

Actual behavior: Nothing happens

Server Setup Information:

Client Setup Information

Desktop App or Browser Version: 2.17.11/3.0 Desktop Operating System: Win 10

Additional context

Relevant logs:

When I send a message with Quote, I get this error in console: 92947462-7767e200-f471-11ea-83f7-79e5ded1ef38

ankar84 commented 4 years ago

Can you check it in web version?

yasirrose commented 4 years ago

@ankar84 @tassoevan . Same behavior in web version.

It is working good for my other college who have version 2.17.11. Quote message is showing properly to him. But it was not working for abdul.rauf OR adil on same version.

yasirrose commented 4 years ago

@ggazzo @MartinSchoeler any update on this. It will be fixed in next release?

damian-centrone commented 3 years ago

this is already fixed. Tested on 3.8.0

yasirrose commented 3 years ago

@damian-centrone

It still has some issue. Please see screencast: https://drive.google.com/file/d/1zt3CmzAX3r6VTBvuURjAzx1mLzlMO7wH/view?usp=sharing

damian-centrone commented 3 years ago

can you share more info of your setup? because I still cant reproduce this. I tested on win, mac, desktop app and browser

yasirrose commented 3 years ago

@damian-centrone My server setup is on Centos 7. I followed this link for setup: https://docs.rocket.chat/installation/manual-installation/centos but with latest node, mongo version. Please see screenshot below for Runtime Environment image

MartinSchoeler commented 3 years ago

Managed to reproduce this problem in 3.8.0. Re opening this issue

yasirrose commented 3 years ago

This issue still exists in 3.9.3.

Darshilp326 commented 3 years ago

Working on it!

himani-mehra commented 2 months ago

Hi @yasirrose , I would love to take on this issue and contribute to the project. Could you please assign it to me if it's available? Looking forward to your response. Thanks!