Not all two-screen forms work because the Autofill algorithm requires a password field to function. This will be solved when the algorithm takes into account the context of the page according to its URL, probably in a library.

This totally works for me in Firefox based browsers (Mull, Fennec, Firefox Beta). There's occasionally breakage with login forms forcing you to type in each TOTP digit separatedly but that's independent from KeePassDX and more depending on the browser and its settings (desktop mode, fingerprint protection, extensions etc.).

Actually, since updating to 4.1.1 it doesn't work anymore. I didn't have this problem with 4.1.0 or 4.0.8.

Autofill at general does not work quite often. Is this a known issue?
Many apps and many web site, even very popular ones like chatgpt.

Actually, since updating to 4.1.1 it doesn't work anymore. I didn't have this problem with 4.1.0 or 4.0.8.

The recognition algorithm hasn't been changed in 4.1.1, I've just tested it and it works well for forms with native browsers but not for browsers with compatibility, like before for paypal.
If you have other general autofill problems, there may be a problem with your device's autofill service.

And I repeat, for forms that require two screens, one for the username/email and the other for the passords, autofill will only work for the password screen because the algorithm doesn't know in advance that the second screen will contain a password.
This can be improved with a dictionary system, but it needs to be encapsulated in a dedicated library.

Since newhinton mentioned Firefox, I tried this in Firefox, Firefox Beta, Fennec and Mull. The KeePassDX-Button appears as soon as I tap on the login field:

What doesn't work anymore is the matching of the URL to the PayPal entry in the KeePass database.

I understand these are technically two separate issues. The issue description is a bit too vague which of the two or both it is.

URL matching works well for me, what URL do you have for Paypal in your entry?

I am using "https://www.paypal.com/signin"

This is how it looks for me:

Above the numbers on the keyboard will be the button for keepass. (Though other keyboards have the same issue with different methods like the popup)

I am using fennec 132.0.0 currently

The same URL that is mentioned in the issue description: https://www.paypal.com/signin

As I wrote in #1820 the algorithm now only seems to work if the path is absent from the URL. With just https://www.paypal.com it should work.

Though that issue seems to be about post-keyboard-popup detection. The problem i have is specificly that the popup doesn't show in the first place, so that subdomain matching is not relevant (or available, since the db is still locked)

I am honestly not even sure if this is a bug in keepassdx at all. It might be an issue somewhere else, because after @J-Jamet overhauled the autotype a couple of months ago, nearly all login types work for me again.

It is just specifically paypal (and my own unraid server) that dont work. Though sadly i don't really know enough about the autotype-service to start debugging this on .y own.

@newhinton What keyboard do you use? I've been using Heliboard. At least in the past, the keyboard or the settings of it seemed to make a different because the suggestion strip seemed to overwrite the KeePassDX button and make it disappear.

At the moment i am using https://github.com/florisboard/florisboard.

However, i only recently started using it. Before i used the grapheneos-default keyboard (which is probably very close to the aosp-default as you can get) and it had the same issue. (that one does not have a "key" for the passwords, but a popup-overlay directly in the content)

I installed florisboard from F-Droid, didn't modify any settings and it works for me as well:

By the way, it does even work in Chrome, after entering some nonsense in the username field and tapping the submit button. Once you get dropped back to the login form, the KeePassDX button appears. The same applies to many other websites with login forms that separate login and password fields (but not all).