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

Text in input field is not erased when switching to other chat #5656

Closed
churik opened this issue Aug 27, 2018 · 3 comments · Fixed by #5946 or #6150
Closed

Text in input field is not erased when switching to other chat #5656

churik opened this issue Aug 27, 2018 · 3 comments · Fixed by #5946 or #6150
Assignees

Comments

@churik
Copy link
Member

churik commented Aug 27, 2018

Description

Type: Bug
Summary: when message field is not empty text should be preserved for selected chat only, so if you are switching to other chat, field should become empty and if you come back again - text should be preserved.
Currently, if text is added in input field, then after switching to another chat - text was preserved. At attempt to send message all text is erased, message is not sent.

Expected behavior

the input field is empty

Actual behavior

text for previous chat is preserved; at attempt to send message text is erased.

Reproduction

  • Open Status Desktop
  • Log in
  • Join to any 2 chats (i.e. #status and #status-desktop)
  • Start typing text in #status (i.e., 1234)
  • Switch to other #status-desktop

Additional Information

Monosnap screenshot tool
Monosnap — the best tool to take & share your screenshots.
@vitvly
Copy link
Contributor

vitvly commented Sep 10, 2018

For now blocked by status-im/react-native-desktop-qt#332

@churik
Copy link
Member Author

churik commented Oct 5, 2018

@rasom
Issue is still reproducible after first logout and it disappears when you select chat again (nightly 05/10/2018).
So, updated steps:

  1. Log in
  2. Select any chat (i.e. #a)
  3. Type message
  4. Switch to other chat (i.e. #b)

Input area in #bcontains text from #a
If you switch back to #a, issue will disappear.
Video: http://take.ms/6lXSv

@churik churik reopened this Oct 5, 2018
@rasom rasom self-assigned this Oct 5, 2018
@rasom
Copy link
Contributor

rasom commented Oct 5, 2018

yep, it was reintroduced actually

rasom added a commit that referenced this issue Oct 5, 2018
yenda pushed a commit that referenced this issue Oct 6, 2018
rasom added a commit that referenced this issue Oct 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants