Bug: Search field loses focus #2347
Replies: 2 comments 3 replies
-
|
Thanks for reporting the issue.
|
Beta Was this translation helpful? Give feedback.
-
|
@abose, I've noticed this issue too. It happens in both the desktop and browser apps. From what I’ve found, here’s the problem: when a user opens the search field, some are in the habit of pressing Ctrl + S to save the file every time. This makes the search field lose focus. This isn’t the expected behavior. The search field should keep focus even after saving. Also, sometimes when pressing Ctrl + F to open the search field, the touchpad gets touched accidentally, which triggers a click event on the editor and makes the search field lose focus. One solution I have in mind is to run a timer of around 200 ms after opening the search field to reject any click events on the editor during that time, since they could be unintentional. |
Beta Was this translation helpful? Give feedback.
-
|
Interesting. May need to track this in some issues if we are not @devvaannsh |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for not providing details. I'm using Phoenix code 4.0.3 for Mac. This issue is really the only issue I have with the software. Here's what happens. If I'm editing a current project got go to the search field, if I type something in and what I've initially typed has a hit somewhere in the project, sometimes (not always) the cursor goes to the match. When I continue typing something (intending it to be part of my search) my keystrokes instead of being entered into the search field goes into the text of the document, sometimes (always?) replacing what the match was. I do have another significant issue, but it's OT for this thread. I don't have any extensions. I've never used find in files. The problem happens most of the time. It's gotten to where I am very careful when using the search feature. Fortunately, undo works, so whenever this happens, I can simply undo to where I was before. I don't believe CTRL-S is involved in my use. OK. I was just really careful when using the search using command-F. I'm currently working on an html document of local helicopters. I pressed command-F and type bell. The bel of what I typed stayed in the search field. But when the second l was typed, what actually happened was that bel in the document was replaced by l, i.e., the second l replaced the bel in the highlighted text and wasn't added to the search. I did not press ctrl-s, I am not using a mouse, and I was careful not to touch the touchpad. I think that what is happening is that focus is changing to the highlighted text in order to highlight it. I wonder if this happens more frequently when typing quickly. I'm a touch typist, so keystrokes are likely to follow quickly. |
Beta Was this translation helpful? Give feedback.
-
|
@victorengel, thank you for such detailed description of the issue. I'll take a look and will try to resolve it asap. Apologies! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm not sure how to replicate this issue intentionally, but it happens a lot unintentionally. I'm using an M4 Mac (Sequoia 15.2). If I press CMD-F to enable the search feature and start typing a search term, often only the first digit is taken by the search field. The remaining digits then get added to the document, which, if I'm not paying attention, likely causes a syntax error. If I notice, it's easy enough to undo and repeat the search, but why is this happening in the first place? It should not happen. This must be some sort of bug with the search field dropping first responder status for some reason.
Beta Was this translation helpful? Give feedback.
All reactions