Steps to reproduce
Environment: running KeyBase Version 6.2.4-20231019211625+5cfcf6b41e (6.2.4-20231019211625+5cfcf6b41e) on Mac
Open the KeyBase UI
Click on the Chat icon in the left navigation menu
Type a term into the Search bar on the top then press the Enter key.
Actual Results
The search term disappears from the search bar on the upper left, but is present in the upper right "Find Next" bar.
Expected Results
The user might expect that tapping "cancel" in the "Find Next" bar would return them to the normal Chat page. But it does not. The only way to return to normal Chat is to click the (X) in the (now empty) Search bar on the upper left.
There should be visible cues 1.) that you are IN search mode and 2.) how to exit search mode and return to normal Chat.
For example, the Search term should still be visible in the upper left search bar.
TBH, it took me a long time to figure this out. I think I used to restart KeyBase whenever it went into this state. I was only reminded of this problem recently when a relatively new hire mentioned that KeyBase would sometimes get into a "bad state" and they couldn't figure out how to get out of it. So now I am reporting it!
Steps to reproduce Environment: running KeyBase Version 6.2.4-20231019211625+5cfcf6b41e (6.2.4-20231019211625+5cfcf6b41e) on Mac Open the KeyBase UI Click on the Chat icon in the left navigation menu Type a term into the Search bar on the top then press the Enter key.
Actual Results The search term disappears from the search bar on the upper left, but is present in the upper right "Find Next" bar.
Expected Results The user might expect that tapping "cancel" in the "Find Next" bar would return them to the normal Chat page. But it does not. The only way to return to normal Chat is to click the (X) in the (now empty) Search bar on the upper left. There should be visible cues 1.) that you are IN search mode and 2.) how to exit search mode and return to normal Chat. For example, the Search term should still be visible in the upper left search bar.
TBH, it took me a long time to figure this out. I think I used to restart KeyBase whenever it went into this state. I was only reminded of this problem recently when a relatively new hire mentioned that KeyBase would sometimes get into a "bad state" and they couldn't figure out how to get out of it. So now I am reporting it!