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

Reactions sometimes counted multiple times in the buttons below messages #11161

Closed
jryans opened this issue Oct 18, 2019 · 5 comments
Closed

Comments

@jryans
Copy link
Collaborator

jryans commented Oct 18, 2019

Not sure of the cause yet, but I have seen (and others have reported) that reactions can be counted twice in the row of buttons below a message.

There are not duplicate reaction events in the timeline when this happens. Refreshing Riot makes the problem go away. Somehow, the Relations structure for the event ends up with several copies of seemingly the same event.

It be best to have a clear reproduction case... Without that, the best I can imagine is just strengthening Relations to ignore events with the same ID as one it already has... It would still be best to understand what's actually going wrong.

@anoadragon453
Copy link
Member

Issue with screenshot and rageshake: #11710

@ara4n
Copy link
Member

ara4n commented Feb 13, 2020

@tredondo
Copy link

tredondo commented May 7, 2020

@jryans: I could reliably reproduce reacting twice with the same emoji to a given message in #13586. Not sure if that is a dupe of this issue, but @turt2live seems to believe so.

@jryans
Copy link
Collaborator Author

jryans commented May 11, 2020

@jryans: I could reliably reproduce reacting twice with the same emoji to a given message in #13586. Not sure if that is a dupe of this issue, but @turt2live seems to believe so.

Looks like that's in fact a separate issue with different emoji character sequences. In any case, thanks for reporting.

@bwindels
Copy link
Contributor

Given that at the time of writing, element web aggregates reactions completely client-side, this must be a client bug. Events in https://github.com/matrix-org/matrix-js-sdk/blob/develop/src/models/relations.js are deduplicated by using a Set, which compares object references to determine identity. So if somehow a reaction snuck in and wasn't deduplicated with an event object we already know about, this could easily happen.

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

No branches or pull requests

5 participants