Launching Console from the GNOME Shell dash using a mouse click does not capture keyboard focus
This is hopefully a very small bug report / usability request, but when launching Console from the GNOME Shell dash via a mouse click, Console does not start capturing the keyboard input straight away. Instead you have to click a second time within the app itself for it to begin capturing keyboard input. This is in stark contrast to launching Console from GNOME Shell using the keyboard (i.e. searching for Console and pressing enter), or strangely, if you use the mouse click to launch console from anywhere 'other' than the dash, in which case Console begins capturing keyboard input straight away.
Likewise, another weird quirk is that the first time you pin Console to the dash, launching it from the dash with a mouse click will continue capturing keyboard inputs straight away for the remainder of that session. But if you log out or reboot the session, launching Console from the dash with a mouse click will go back to not capturing the keyboard input.
So there seems to be some weird interaction with Console being pinned to the dash and the state in which it launches.
Other apps, such as GNOME Text Editor will capture keyboard input straight away, regardless of which way they are launched. I can't get this behavior to appear in any other GNOME apps that I have tried that have some sort of primary keyboard entry element. Even apps like GNOME Software will capture keyboard entry straight away and use it to populate the search box.
Here is a recording where I demonstrate the above issue on a session that already has Console pinned to the dash.
Screencast_from_2023-05-11_17-43-58
My system is running Arch Linux with GNOME 44.1 on a Wayland session. That said, I experienced this same issue for the whole time I was on GNOME 43 as well.