Make the completion usable with the mouse

[HunterGraubard]

I would like to see better mouse support for qutebrowser.

I understand that qutebrowser is designed to be a Vim-like keyboard-focused browser, and that's fine (and exactly what I want). However, "keyboard-focused" doesn't have to mean "unusable with a mouse". Sometimes a person just can't use either a keyboard or mouse for whatever reason, even if only temporarily. I believe that all good user interfaces should be usable with both mouse and keyboard. At the very least, the core functions should be available with both input devices, if not everything.

Unless I'm just missing something, I can't find any way to perform some major, basic tasks via mouse, such as changing URL, loading bookmarks, navigating forward/back, etc. In fact, from what I can see, pretty much the only things you can do by mouse are reload the page, follow links, or close tabs by middle-clicking them.

I propose a very simple way to add some basic mouse support to qutebrowser:

1. Mouse-clicks in the bottom-left corner (on the status bar) should open the command prompt, along with its list of suggestions, exactly as if you had pressed the ":" key.

2. Clicking in the main browser area should close the command prompt and suggestions list.

3. Double-clicking one of the command suggestions should immediately RUN that command. Currently, the suggestions list only supports single-clicks, and all that does is copy the command to the prompt at the bottom - but you can't actually do anything with it unless you use the keyboard.

4. Add a "Run Command" menu item to the command prompt's right-click menu, or alternatively, add a "Go" button to the command prompt that only appears if you opened the command prompt by mouse in the first place.

By adding just these small bits of mouse-support, it would suddenly open up many of the commands to mouse-only users. I know that not all commands can be simply run without adding any extra parameters, but many of them can be (e.g. "fullscreen", "close", "tab-clone", "back", "forward", "reload", etc.).

For the commands that can't be run without any extra input, mouse-users can complete the rest of the command by pasting text or by using an OSK. The fourth suggestion above is to allow mouse users to run a command after completing it.

These changes would not harm the keyboard side of things, and keyboard-only users would never have to see any difference.

[The-Compiler]

Those all seem sensible (apart of 4, which seems a bit of a stretch - you might as well just press enter in the OSK if you're using one).

However, don't expect me to work on this anytime soon - contributions would be welcome though! 😉

[The-Compiler]

In a similar vein, prompts should probably be close-able via the mouse as well, by making the actions (which are shown with their keybindings) clickable.

Thanks to pruhnab over at the Open Source Design Discourse for the idea!