On my Mac, cmd+shift+f opens up a code search tab and focuses on the search text box. However, if you already have a code search tab open and it’s not the active tab, then cmd+shift+f re-opens the code search tab but doesn’t focus on the search input box.
cmd+shift+f for code search should always behave in the same way, ideally it should always focus on the search input field so I can start typing immediately
cmd+shift+f focuses on the input field if there is no existing code search tab, but doesn’t if there is one. The result is that I often hit cmd+shift+f and start typing a query, realise it wasn’t focused, and focus on the search box, but have also inadvertently injected random letters into my codebase in whatever file I was previously on, and then have to hunt to correct the error
Steps to reproduce:
Open up a code search tab and then open up any other tab. Hit cmd+shift+f. The code search tab appears again, but the input isn’t focused on.
M1 MacBook / safari