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

Nested rich replies are an endless ping fest. #5968

Closed
turt2live opened this issue Jan 11, 2018 · 2 comments
Closed

Nested rich replies are an endless ping fest. #5968

turt2live opened this issue Jan 11, 2018 · 2 comments
Labels
A-Notifications A-Replies reply P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@turt2live
Copy link
Member

Description

Decided to test this in offtopic and we ended up with a 3-level nested reply that was still pining richvdh.

Steps to reproduce

  • Send a message with a ping to someone
  • Reply to it
  • Reply to the reply
  • Reply to the replied reply
  • and so on

It should probably not ping unless you are in the immediate reply?

Version information

  • Platform: web (in-browser)
  • Browser: Chrome 63
  • OS: Windows 10
  • URL: riot.im/develop
@t3chguy
Copy link
Member

t3chguy commented Jan 13, 2018

This will be caused by the imperfect plaintext representation, so related to #5974

@t3chguy
Copy link
Member

t3chguy commented May 4, 2018

Fixed by merged PR

@t3chguy t3chguy closed this as completed May 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Notifications A-Replies reply P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Development

No branches or pull requests

3 participants