Description
When a Party or Guild leader removes a member from a Party or Guild, the member they select IS removed but the website initially shows that a different member was removed. When you reload, you see that only the selected member was removed.
Steps to reproduce:
- Go to the Guild or Party and click on the "Member List" badge. (For a Party, you can also click the "View Party" button in the header.)
- When the list of members appears, select one member that you want to remove.
- (Optional) Take note of all the other members that appear on that screen. This is easiest in a small group of course.
- Click on the three-dots button for that person and select "Remove Member".
- Click the "Yes, remove them" button.
- Observe that that person still appears in the list. This is part of the bug.
- Observe that a different person has disappeared from the list. This is the other part of the bug.
- Reload the website with your browser's refresh button.
- Observe that that person you tried to remove is no longer in the list. This shows that it is only a client-side bug, not an API bug.
- Observe that the different person who appeared to be incorrectly removed is still in the list (this is good).
Thanks to citrusella for reporting this. Below is her report with what she observed. The information above is what I observed when I confirmed it.
A strange issue with the party member modal, at least as clicked from the "view party" button in the header, when removing members: It always removed the bottommost member from the list (even if a different member was the one actually removed).
The first time I did this, it looked like it removed a different member and then removing the member I had originally intended to remove didn't work because they were no longer there (and the other member was missing from the modal). The second time this happened, it looked like I removed myself from the party, which caused a minor freakout on my part. It happened the same after a reload so I don't think it was exactly some sort of cache issue or anything (I reloaded to make sure the member modal was up-to-date after the first time, so I don't know if a sync would have fixed it). In both cases the intended member was the one actually removed and the different member disappearing from the list was purely a visual bug.