Can you reproduce the bug on the Forgejo test instance?
No
Description
Reproduce:
- choose an issue comment with an existing reaction
- add the same reaction
- use the dropdown on the top right of the comment box to remove the reaction
- observe that both reactions are gone now
I was not yet able to reproduce with actual issues (the first comment), only further comments. forgejo/discussions#194 is a thread with plenty of them to test.
It looks like the unwatch action is always firing "react" instead of "unreact" in the dropdown. The response looks like this:
POST https://codeberg.org/forgejo/discussions/comments/2110153/reactions/react
{"empty":true,"html":""}
It also gets rid of any other reaction in case there is some (not only the same emoji type).
Screenshots
An example comment that has one other reaction (which is now gone for me)
Forgejo Version
8.0 (Codeberg)
Browser Version
Firefox 128
### Can you reproduce the bug on the Forgejo test instance?
No
### Description
Reproduce:
1. choose an issue comment with an existing reaction
2. add the same reaction
3. use the dropdown on the top right of the comment box to remove the reaction
4. observe that both reactions are gone now
I was not yet able to reproduce with actual issues (the first comment), only further comments. https://codeberg.org/forgejo/discussions/issues/194 is a thread with plenty of them to test.
It looks like the unwatch action is always firing "react" instead of "unreact" in the dropdown. The response looks like this:
~~~
POST https://codeberg.org/forgejo/discussions/comments/2110153/reactions/react
{"empty":true,"html":""}
~~~
It also gets rid of any other reaction in case there is some (not only the same emoji type).
### Screenshots
An [example comment](https://codeberg.org/forgejo/discussions/issues/194#issuecomment-2149554) that has one other reaction (which is now gone for me)
### Forgejo Version
8.0 (Codeberg)
### Browser Version
Firefox 128
21 KiB