-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
inviting someone already in room fails blindly #3968
Closed
Comments
lampholder
added
T-Defect
S-Minor
Impairs non-critical functionality or suitable workarounds exist
P2
ui/ux
labels
May 22, 2017
I'm not sure what the best fix to this would look like - our options seem to be:
Both seem quite... big for something you could safely ignore. Thoughts? |
Agreed, did confuse me for a good 60 seconds before I figured out the person was already in the room |
worth noting that this doesn't apply if someone uses the |
turt2live
added a commit
to matrix-org/matrix-react-sdk
that referenced
this issue
Nov 29, 2018
Fixes element-hq/element-web#3283 Fixes element-hq/element-web#3968 Fixes element-hq/element-web#4308 Fixes element-hq/element-web#1597 Fixes element-hq/element-web#6790 This does 3 things: * Makes the `MultiInviter` check for a user profile before attempting an invite. This is to prove the user exists. * Use the `MultiInviter` everywhere to avoid duplicating the logic. Although a couple places only invite one user, it is still worthwhile. * Communicate errors from the `MultiInviter` to the user in all cases. This is done through dialogs, where some existed previously but were not invoked. Specifically to the 403 error not working: What was happening was the `MultiInviter` loop was setting the `fatal` flag, but that didn't resolve the promise it stored. This caused a promise to always be open, therefore never hitting a dialog.
Fixed by matrix-org/matrix-react-sdk#2317 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
no way of knowing what happened without looking at the error in network tab of dev tools
The text was updated successfully, but these errors were encountered: