[GH-ISSUE #1081] [Bug] Time input field cannot recover from bad input #430

New issue

Closed

opened 2026-03-23 20:36:31 +00:00 by mirror · 1 comment

mirror commented

2026-03-23 20:36:31 +00:00

Owner

Originally created by @richardshiue on GitHub (Sep 17, 2022).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/1081

Originally assigned to: @appflowy on GitHub.

Describe the bug
The text field used to input the time fora grid's date cell turns red and displays an error message if the submitted time isn't acceptable. However, entering a valid time after doesn't cause the text field to return to normal, even though the input is now correctly displayed in the cell.

To Reproduce
Steps to reproduce the behavior:

Open a grid cell with date property
Enable Include Time
type gibberish into the text field and submit
type a correct time into the text field and submit
Observe text field

Expected behavior
The text field should have a blue border and no error text

Desktop (please complete the following information):

Linux
0.0.5, main

Originally created by @richardshiue on GitHub (Sep 17, 2022). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/1081 Originally assigned to: @appflowy on GitHub. **Describe the bug** The text field used to input the time fora grid's date cell turns red and displays an error message if the submitted time isn't acceptable. However, entering a valid time after doesn't cause the text field to return to normal, even though the input is now correctly displayed in the cell. **To Reproduce** Steps to reproduce the behavior: 1. Open a grid cell with date property 2. Enable `Include Time` 3. type gibberish into the text field and submit 4. type a correct time into the text field and submit 5. Observe text field **Expected behavior** The text field should have a blue border and no error text **Desktop (please complete the following information):** - Linux - 0.0.5, main

mirror

2026-03-23 20:36:31 +00:00

closed this issue
added the
bug
label

mirror commented

2026-03-23 20:36:32 +00:00

Author

Owner

@richardshiue commented on GitHub (Sep 29, 2022):

I can no longer reproduce this issue on main and 0.0.5.3. Should be good to close

@richardshiue commented on GitHub (Sep 29, 2022): I can no longer reproduce this issue on main and 0.0.5.3. Should be good to close