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
Replace dialog opens with the wrong field focused #4566
Comments
This applies across OS's, I also think this is as designed. Might be worth a little discussion with the feature owner though. Note that you can always use ctrl+f to focus find from anywhere. |
@Tyriar ah, thanks. I've added a list of editor software that focuses on Find first. |
Atom 1.5.3 focuses find first too. |
I agree, this behavior is counter-intuitive. I realized I run into my issue (of the find widget not trapping focus) a lot because I'm accustomed to hitting If this issue was fixed, I probably wouldn't run into my issue as often. |
More examples: Focuses Find input on
Focuses Replace input on
|
It took me time to get used to using ctrl+f to focus the find field and ctrl+h to focus the replace field. Now I prefer it; it beats tabbing. |
this issue is talking about the same thing as #17562 . From tomorrow's insiders, if current selection and the existing search string in Find Widget are empty, we'll focus the Find Input first. Close it first and please let me know if you have any idea about that. |
Steps to Reproduce:
CTRL-H
for Find & Replace pop-upScreen grab of the issue:
Issue: Notice the Find field should be focused first when the dialog is opened. Instead, the Replace field is focused. And
tab
moves the focus forward, to the little icons (one would have to know toshift-tab
to get back to Find.)ETA: Ah, I suppose this changed at some point, I was comparing 0.10.11 Linux to 0.10.3 Windows.
So it becomes a question of which implementation is "more better". :p :)
Alright, well, here's a list of editor software that focuses the Find input when pressing
Ctrl-H
:Vs. editors that focus Replace first:
Feel free to bring others to my attention.
The text was updated successfully, but these errors were encountered: