When the hover is focused, keyboard shortcut to autofix (ctrl + .) does not work

[CWEzio]

When the hover is focused with pressing ctrl + k ctrl + I twice, the autofix shortcut no longer works. Maybe this is because when the hover is focused, the problem is no longer being focused. However, this behavior does not follow intuition and it would be nice to still be able to use the autofix shortcut key after the hover is focused.

vscode version: 1.96.0

[aiday-mar]

Hi thank you for filing this issue. Yes that is correct, the cursor is no longer present in the editor, the editor is not focused, so the auto fix shortcut can not be used. I will think about this.

[CWEzio]

Thank you for your consideration. I think it would be handy to be able to use the autofix key when the hover is focused for a workflow using only keyboard: open the hover, scroll it to read (it is only possible to scroll the hover using keyboard when it is focused) and check the autofix solution.

[mherrerarendon]

Another symptom of the hover not being focused is that the hover won't exit when pressing escape. This is not ideal especially if you've configured vscode to use the mouse minimally, since you now need to use the mouse to focus the hover and then escape to close it.

[aiday-mar]

Hi @mherrerarendon thank you for the comment. What you are describing is I believe a bug that should be fixed in latest nightly releases and the next stable releases. It is yet another issue unrelated to the one above.

[mherrerarendon]

Hi @mherrerarendon thank you for the comment. What you are describing is I believe a bug that should be fixed in latest nightly releases and the next stable releases. It is yet another issue unrelated to the one above.

Excellent, thank you @aiday-mar !

[aiday-mar]

Hi after thinking some more I am not sure if it would be desirable behavior to open the autofix menu when the hover is focused. The autofix menu requires the editor to be focused for it to work. I will close this issue but will keep an eye on if other similar issues are filed.

Concerning the issue mentioned by @mherrerarendon I believe it should be fixed now.