Closed PingWIN7 closed 6 years ago
also bugs out the pie chart if the fob number is higher than the user count.
AttendeeController -> Refresh should send current session info and check if the attendee is still in the meeting (in list). In case he isn't then we should re-add the user into it so it does not bugs out the counter (or not that badly)
In case the user pressed the fob button we should also check if the user is in the meeting. In case the user is not in the meeting we should re-add him. (Fob->meeting->attendee)
With the recent changes I've made this should no longer be an issue.
Situation: Double connection from same browser, from one instance he leaves the meeting. It would result in a fob that will be not removed, the user count is at 0. On the other instance the user is still present in the meeting room. It can also fob on new topics. Rejoining the meeting on that browser does not fix the wrong counter issue.