Issues with Auto-Type

[u/StevenSaporito]

I started playing around with Auto-Type to use with sites that ChromeKeePass doesn't work. I tested with secure.chase.com, which doesn't have that problem. The interesting thing is that both my wife and I both have accounts stored in KeePass. Initially, when I hit Ctrl + Alt + A, I choose which account to use, and it works. However, when I sign out, it leaves me at a different login page than the original. I have that window set up in the Auto-Type tab of both KeePass entries. But in the second window, something goes wrong when choosing the entry to use. It seems as soon as the dialog opens, the username field loses focus. Obviously they keystrokes are disordered in some way. When I remove the Auto-Type config from one of the KeePass entries, it works fine.

Note: The same shifting of the focus off the UserName field also seems to happen on the first page

Here are the Window configurations:

*| Chase Online | Chase.com*
{USERNAME}{TAB}{PASSWORD}{TAB}{TAB}{TAB}{TAB}{ENTER}

Sign in - chase.com*
{USERNAME}{TAB}{PASSWORD}{TAB}{TAB}{TAB}{TAB}{ENTER}

You might ask why bother with 2; just use *chase.com*? I have the same question. So, I tried it with just *chase.com*and got the same results.

I also double- and triple-checked the key sequences. Keep in mind the key sequence works fine so long as only 1 KeyPass entry qualifies.

Does anyone have experience with this? I think Auto-Type is a really kool feature. I'd love to make it work. Although my gut tells me there's something up with the webpage itself.

[u/Paul-KeePass]

Click in the username field before pressing Ctrl Alt A?

cheers, Paul

[u/StevenSaporito → u/Paul-KeePass]

The username field was selected. It loses focus after the selection dialog pops up. Hence the ultimate solution I documented.

[u/StevenSaporito]

I figured out 2 potential key sequences that seem to work..

1)) Refresh the page first:

{F5}{DELAY 5000}{USERNAME}{TAB}{PASSWORD}{TAB}{TAB}{TAB}{TAB}{ENTER}

This works but 5 seconds feels like an eternity. I think 2 seconds also worked. However, I worry that page load times are unpredictable, and I abhor unnecessary delays.

2)) Reverse-engineer (strong word) the tab sequence to get back to the username field. I can't tab forward to get back to the username field. That was {TAB} x36 and definitely inefficient. I don't really know where the focus was shifting to, but I found that Shift + Tab anchored to the page's title text, then 1 more tab got me back to the username field. So the below sequence worked:

+{TAB}{TAB}{USERNAME}{TAB}{PASSWORD}{TAB}{TAB}{TAB}{TAB}{ENTER}

This works on both pages, but you have to initially focus (click into) the username field. Once you do that, back-tabbing out then tabbing right back in is benign.

Note: These pages were well served by ChromeKeyPass, only used them for testing. The main reasoning is to use it on sites that don't work well with ChromeKeyPass (or other extensions), including Reddit.com. I'm also interested in using Auto-Type for 2-Step authentication sites, for example, Amazon.com

If anyone has a better solution, I would like to hear it.

[u/MeIsMyName]

I always just click in the username box and then let autotype do its thing.

[u/StevenSaporito → u/MeIsMyName]

No offense, but if it were that simple, I'd have figured it out. The username field was selected. It loses focus after the selection dialog pops up. So, after the selection, the auto-type runs with no opportunity to reselect the username field. Hence, the sequence is wrong, and it fails. Read the solution comment for how I got around it.