Re: [w3c/payment-request] Browser autofill unavailable for payment apps (Issue #1049)

stephenmcgruer left a comment (w3c/payment-request#1049)

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' ?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/issues/1049#issuecomment-3428379221
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/payment-request/issues/1049/3428379221@github.com>