fix(guests): Don't force remove guests but leave it to the "purge logic" #13980
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently guests with a display name are not cleaned up, to keep their name for chat messages and other activity.
👣 Steps
The main difference is that Firefox seems to keep the session and is still recognized as the previous guest, chrome creates a new attendees entry on each reload
🛠️ API Checklist
🏁 Checklist
docs/
has been updated or is not required