-
Notifications
You must be signed in to change notification settings - Fork 499
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
Hard to predictably tap “Local contacts” on People tab #4523
Comments
@pixlwave thank you. So I think we're best to not have an invites header, if thats happening also on the Rooms tab. Just noticed the invite for people says has "user invited you". Maybe neither of us knows but would be good if someone could confirm if other people can invite you to chat with a third person? Otherwise, it's maybe redundant info and needs a redesign. Removing the contacts section makes a lot of sense to me (third image)
One thing we lose by removing the contacts section is a state for when we don't have contacts access, to encourage it. |
👍
Just checked and inviting a third user into an existing conversation actually sends the invite through as a room invite. Not sure if that's technically a bug, I will look into this tomorrow.
Would this essentially be ticking the "Matrix users only" checkbox by default, and then hiding the header?
|
This behaviour matches Android too. It seems the spec only has the functionality to invite someone into a direct conversation when creating the room and not after the fact. |
It would be pretty much that but I think that's a bigger change that would need more consideration from a product pov |
Got it. So as part of this, remove the section with a view of a filtered section possibly coming back in the future? |
Similar to #4521 tapping the section name can result in tapping the "Matrix users only" checkbox.
Removal of section might help.
The header for the Conversations section could then go too, however when there is an invite a second section will be added.
From: @niquewoodhouse
The text was updated successfully, but these errors were encountered: