RFC: Improved per entry Auto-Type

[hifi]

Summary

I'm proposing per entry Auto-Type would be changed to present a list of windows that can be auto-typed into creating a dialog that resembles the global Auto-Type dialog but windows instead of entries. The window list shall be filtered with window associations for the entry if they exist.

The window list should behave as follows:

1. if an entry has window associations and they match a single window, type into it automatically (honor "Always ask before performing Auto-Type", skip dialog only if not enabled)
2. if entry has window associations and they match multiple windows, show them in the dialog
3. if entry has no window associations, list all windows that can be typed into (skip docks etc.)

Always order the list by whatever the WM/desktop thinks is the focus order for alt-tab so that the first entry is the previously focused one and highlight it by default (aka first entry). This keeps current behavior while also providing more functionality and security by having the window title shown, albeit in a list. You can just hit enter to accept the default selection.

In my opinion this would supersede #6205 and #6206 while also providing more functionality and security instead of relying on deny lists or timers.

Examples

Imagine a dialog with a list of window titles (and icons if possible) like a task switcher, based on global Auto-Type

It possibly needs to include a checkbox like the global Auto-Type but: [X] Search all open windows to have an override if the window associations are bad. Have it disabled completely if no associations are configured for the entry.

Context

Current behavior of typing to the previous active window has multiple disadvantages:

• it might not be what you expect
• it's not shown which window it was (though easily fixable)
• it's hard to control reliably by the user
• "focus follows mouse" can break it completely

Most of these are both security and usability concerns in my opinion. I avoid using it for pretty much because all of them.

[MKobek]

Hey @hifi How much time and which skill level is required to get that implemented. Maybe I get a volunteer to build that.

[hifi]

Basic understanding of Qt5 and GUIs for the UI part. Some platform (Windows, Linux/BSD/X11 or MacOS) knowledge to at least get one platform working with it.

It's mostly just implementing an abstraction to list windows and then display them. I make it sound easy but it really depends on the developer's experience.

[droidmonkey]

@hifi do we still want to spend time on this?

[hifi]

I still think this might be a good way to improve entry level usage. I'd keep this issue around for now.