**Issue: **
When triggered from within KeePass 2, using the keyboard shortcut Ctrl+V with an entry highlighted, Auto-Type ignores all {DELAY XXXX} commands and types as fast as it can.
Background:
I have to deal with some modern web design where everything you enter is on a separate page that is extra slow to load, so there's a significant delay between the username entry before a password can be entered. All of this is happening in a Window with no title that can't be targeted by KeePass 2 directly, so I have configured the default Auto-Type command for this entry to:
{DELAY 5000}{USERNAME}{TAB}+{TAB}{ENTER}{DELAY 5000}{PASSWORD}{ENTER}
**Expected result: **
The above default Auto-Type entry should allow me to trigger Auto-Type with Ctrl+V, switch to the window, that's awaiting my username, have KeePass enter said username and trigger the next screen, then wait for the password screen to load and enter that.
Actual result:
KeePass 2 starts typing immediately, giving me no chance to switch to the window. In addition, it also ignores the delay between Username and Password and immediately starts typing the password before the window is finished loading the appropriate entry form. KeePass 2 seems to be ignoring/skipping all the {DELAY 5000} commands.
Keepass 2 version: 2.57.1 (64-bit)
OS: Windows 11 Enterprise (23H2)
I suspect you have left the default Auto-Type sequence in place and that is what is used.
BTW, pressing Ctrl V will cause KeePass to drop to the background. No need to switch manually.
cheers, Paul
I specifically overrode the default ("Override default sequence" is checked and the sequence I pasted above is in the field below it).
Strangely enough, after a forced reboot, and thus restart of KeePass 2, it is now working correctly. I am no longer able to reproduce the issue.
Unfortunately, this particular window (opening from PowerShell) is "Always on top" and as soon as you click out of it (to go to KeePass for example), the input field loses focus and does not regain it when the window becomes the main one again (you must click the field to place the cursor back into it).
Bug can be closed. Unable to reproduce after reboot/restart.