Microsoft Windows [Version 10.0.18363.900]
PowerToys version: 0.19.1
PowerToy module for which you are reporting the bug (if applicable): PowerToys Run
When I activate PT Run with the Alt-Space hot-key, the application does not always place the cursor in the search box.
When I press Alt-Space, PT Run appears. However, often and without an apparent pattern, the cursor will not be active in the search dialog box. I need to manual click in the search dialog box before I can type the search letters.
I expect the cursor will always be placed in the search dialog box and ready for me to type, whenever I activate PT Run with the hot-key.
UPDATE: The issue occurs when the last PT Run search result was selected with the mouse.
Steps to reproduce:
Expected result:
At step 4, I expect the search dialog box is activate with the cursor inside it so I can immediately start typing a search query.
Cheers!
Brad
Clarification: At step 4, after typing Alt-Space, I expect the search dialog box to have the focus with the typing cursor placed inside so I can immediately start typing a new search query. This is essentially the behaviour you currently get if the previous search result was selected using keyboard arrows (instead of the mouse).
I am having the same experience with PT Run, the typing cursor is not automatically within the search box when PT run is activated, so I have to click on it to start typing. I did not have this behaviour with the release 0.18.2
I am having the same experience with PT Run, the typing cursor is not automatically within the search box when PT run is activated, so I have to click on it to start typing. I did not have this behaviour with the release 0.18.2
Same here.
See also: #4891
@crutkas Many thanks for adding this to the v0.21 release.
Yeah, i can repro this with the steps for @phabguy did. We don't force the focus here then from the mouse click.
@somil55 / @alekhyareddy28 fyi. mouse based interaction for list directly causes this behavior
We just released 0.20 and this should be resolved there. Please try it out.
Tested it with 0.20 and it appears to be fixed, thanks so much!!
Most helpful comment
Yeah, i can repro this with the steps for @phabguy did. We don't force the focus here then from the mouse click.
@somil55 / @alekhyareddy28 fyi. mouse based interaction for list directly causes this behavior