Skip to content
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

Input is hidden in rooms with one participant #208

Open
jadyndev opened this issue Sep 18, 2023 · 4 comments
Open

Input is hidden in rooms with one participant #208

jadyndev opened this issue Sep 18, 2023 · 4 comments
Labels
bug Something isn't working upstream This issue is also applicable upstream

Comments

@jadyndev
Copy link

jadyndev commented Sep 18, 2023

Describe the bug
The text input is hidden in rooms with exactly one participant.

To Reproduce
Steps to reproduce the behavior:

  1. Create a room with just yourself
  2. Enter the chat
  3. Convert it into a DM (/converttodm)

Expected behavior
The input seems to exist, it is shown briefly when entering the chat from the menu and there is a blank area at the bottom where the input would be.

Screenshots
Screenshot

Smartphone:

  • Device: OnePlus Nord 2
  • OS: Oxygen OS 13.0

Additional context

  • App version: 1.6.5.sc71 [40101212] (F-b98153c4)
  • Store: F-Droid
  • Related labs settings: rich text editor is enabled

Upstream relevance
unknown

@SpiritCroc SpiritCroc added bug Something isn't working upstream This issue is also applicable upstream labels Sep 19, 2023
@SpiritCroc
Copy link
Member

SpiritCroc commented Sep 19, 2023

Apparently, Element assumes you created a DM using invite-by-mail if no users are currently invited to the DM and only one user is in it: 94675b9
- in which case it makes sense to prevent you from writing messages that nobody will read.

What's the benefit of marking a one-person chat as DM? 🤔
Anyway, sounds like a "misuse" of the DM flag - which isn't bad per say, but that makes this bug not a high-priority to fix.

@jadyndev
Copy link
Author

jadyndev commented Sep 19, 2023

Element Desktop doesn't show this behavior, which is a bit inconsistent.
I'm using such a room to share files and text between multiple devices, it's not the best solution but I have some kind of matrix client pretty much everywhere.

I wouldn't consider this a misuse of the direct flag, as the specification states:

This does not restrict the chat to being between exactly two people [...]
Client Server API 11.25

@SpiritCroc
Copy link
Member

SpiritCroc commented Sep 19, 2023

I'm using such a room to share files and text between multiple devices, it's not the best solution but I have some kind of matrix client pretty much everywhere.

Doesn't explain to me the benefit of flagging it as "direct" vs not doing so, at least in a usual SchildiChat-setup where you have all chats in one list instead of separate DMs in the overview.
Obviously it's still a bug :)

@jun10r4lm31d4
Copy link

> > I'm using such a room to share files and text between multiple devices, it's not the best solution but I have some kind of matrix client pretty much everywhere.

Doesn't explain to me the benefit of flagging it as "direct" vs not doing so, at least in a usual SchildiChat-setup where you have all chats in one list instead of separate DMs in the overview. Obviously it's still a bug :)

For me the is the ability to silence notifications of groups and allow for chats.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working upstream This issue is also applicable upstream
Projects
None yet
Development

No branches or pull requests

3 participants