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.

Sign up for GitHub

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

Jump to bottom

[BUG] New chirp input not cleared after send #1863

Closed
2 of 6 tasks
4xiom5 opened this issue May 16, 2024 · 1 comment
Closed
2 of 6 tasks

[BUG] New chirp input not cleared after send #1863

4xiom5 opened this issue May 16, 2024 · 1 comment
Assignees
@4xiom5
Labels
bug Something isn't working fe1-web

Comments

@4xiom5
Copy link
Contributor

4xiom5 commented May 16, 2024

Description (Actual behavior)

After sending a new chirp, the text input is not cleared.

Expected behavior

The text input should be cleared after a new chirp is sent.

How to reproduce

Send a new chirp.

Version & Environment

This bug was reproduced on:

Front-ends:
  • Fe1-Web
  • Fe2-Android (please specify if phone or emulation, and Android version)
  • Not applicable
Back-ends:
  • Be1-Go
  • Be2-Scala
  • Not applicable

Impact

Reduced usability
@4xiom5 4xiom5 added bug Something isn't working fe1-web labels May 16, 2024
@4xiom5 4xiom5 self-assigned this May 16, 2024
@4xiom5
Copy link
Contributor Author

4xiom5 commented May 22, 2024

Caused by issue #1860

@4xiom5 4xiom5 closed this as completed May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@4xiom5 4xiom5

Labels
bug Something isn't working fe1-web
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@4xiom5