Autotype not working in Firefox 60+ on Linux

[bernermic]

Since some time (maybe since updating to Firefox 60.0.x June 6.) I face the issue, that the autotype password to Firefox password fields is not working anymore (at least for most of my passwords).

Expected Behavior

Opening login page - call to auto type fills out username & password automatically and submits the login call. Login is executed properly.

Current Behavior

Opening the login page + call to auto type fills in the user, then the password and submits the form. Response is: "Invalid login or password".
On checking what happens I found this:
User is typed in correctly,
Password as in my tests I found out the first character of the password is not typed.

Further tests showed, that this happens after each TAB execution. Somehow this leads to character missing

Further tests again showed, that more characters where not typed. Example pattern tested was:

• Form with three input form fields.
• Pattern for auto type: {USERNAME}{TAB}12{TAB}{PASSWORD}
  -- Elements should be:
  USERNAME="user"
  12="12"
  PASSWORD="password"
• Result in form was:
  -- USERNAME=correct
  -- 12=only character '2' was filled - one character was missing
  -- PASSWORD="word"
  So it is not allways just one character which is not typed.

Possible Solution

Steps to Reproduce (for bugs)

1. Firefox version 60.0.2
2. Keepassxc 2.3.3 (installed as Snap)
3. Ubuntu 18.04
4. Autotype password via default pattern: {USERNAME}{TAB}{PASSWORD}
5. verify what was typed as password

Context

Debug Info

KeePassXC - Version 2.3.3
Revision: 0a155d8
Distribution: Snap

Libraries:

• Qt 5.7.1
• libgcrypt 1.7.6-beta

Operating system: Ubuntu 18.04 - installed via Snap (Snap based on: Ubuntu Core 16)
CPU architecture: x86_64
Kernel: linux 4.15.0-23-generic

Enabled extensions:

• Auto-Type
• Browser Integration
• Legacy Browser Integration (KeePassHTTP)
• SSH Agent
• YubiKey

[droidmonkey]

Wow that is stupid. Firefox must be blocking input for a short period of time after pressing TAB. If you add a {DELAY 1} in there, it types perfectly.

{USERNAME}{TAB}{DELAY 500}{PASSWORD}{ENTER}

OR

Increase the typing delay in settings to 50ms

[bernermic]

Oh - thanks for this response. I did not think of such a test.
I'll try that and if it works I report it back to you.

[bernermic]

This workaround seems to work consistently for me now.
I tested both DELAY in Autotype sequence and time 50 ms delay globally.

[jimbudarz]

Settings don't have a "pattern" option on the Auto-Type settings tab. Where are users supposed to change this?

[droidmonkey]

That can be done on the root group to impact all entries, or per entry.

[jimbudarz]

For future users who experience this bug, this is accomplished by:

1. Right click on "Root" folder (or another folder if you prefer to limit the pause to a subset of saved passwords.)
2. Click "Edit Group"
3. Under Auto-Type, select the radio button "Set default Auto-Type sequence" to {USERNAME}{TAB}{DELAY 500}{PASSWORD}{ENTER}
4. Apply changes.

Note: Maybe default behavior for the root folder should be shifted to Application Settings.
Edit: Initial post said DELAY 1. Should be 500 since unit is milliseconds.

[jimbudarz]

The problem persists for me after applying the suggested workaround. The current Root folder Auto-Type sequence is {USERNAME}{TAB}{DELAY 1}{PASSWORD}{ENTER} and I can confirm that the setting has been inherited by individual entries but there appears to be no delay- even with {DELAY 100} I get no perceptible time between entry of username and password. The example site where this doesn't work is reddit.com.

[droidmonkey]

This is because I gave bad advice, the DELAY keyword is actually in milliseconds, so using {DELAY 500}
(ie, 0.5 seconds) should be sufficient.

[jimbudarz]

Thanks @droidmonkey for sticking it out with me. Situation resolved.

[bernermic]

For me the DELAY 1 is working reproducable.
That is strange.

[mihaiile]

shouldn't the typing delay automatically be applied also for the {TAB}?
By default the application has a start delay of 500ms and typing delay of 25ms.
I would guess that the 25ms of delay should be applied not only after letters input but also for tab command.

[droidmonkey]

That is where I think the issue is, the delay is not applying correctly between actions. Perhaps we need to also increase the default delay after a tab event. I'm opening a new issue to capture that action.