Browser autofill unavailable for payment apps

[dtjones404]

Browser autofill functionality appears to be disabled or non-functional when payment applications are running within Chromium's implementation of the PaymentRequest API payment window. This significantly impacts user experience by preventing users from leveraging saved emails and passwords. Is this an intentional limitation of the spec? I've attached some screenshots to illustrate this behavior affecting Google Pay, but it appears to be a general issue as it's affecting our app as well.

Google Pay running in a popup window (autofill available):

Google Pay running in the PaymentRequest browser window (autofill unavailable):

[ianbjacobs]

cc @rsolomakhin, @stephenmcgruer

[gregjopa]

@dtjones404 could you also test out passkeys in Chrome to see if they work with the payment request popup?

[dtjones404]

@gregjopa I did some testing passkeys don't seem to be working either

[stephenmcgruer]

Hey folks; thanks for filing the issue and apologies for the delay in getting back to y'all! These are effectively Chrome bugs rather than spec bugs, as far as I know.

Lack of support for Autofill in Payment Handler windows is a known issue - I've filed https://crbug.com/453958054 to track this issue. It will be unfortunately tricky to fix as the Payment Handler window in Chrome is somewhat 'special' and is not equivalent to a 'real' tab (see the lack of omnibox, etc).

For passkeys, I'm actually trying to understand what level of support is available in Payment Handler windows currently. I was able to make https://webauthn.io/ work in a Payment Handler on MacOS Chrome at least, both for registering and authenticating, but I'm not sure if that will be true on other platforms (e.g., Windows, Linux). I did test and discover that the Autofill-like conditional UI does not work, likely for the same reason as Autofill (filed https://crbug.com/453958056). Is conditional mediation what you meant by "passkeys don't seem to be working either' ?

[marcoscaceres]

This seems like outside of the scope of the spec.

@stephenmcgruer, given the related chrome issues file, can we close this?

[stephenmcgruer]

@stephenmcgruer, given the related chrome issues file, can we close this?

Yep, closing.