[WPWG] "Shared Autofill" proposal / TAG review

Hi folks,

I wanted to let you know about an ongoing W3C TAG review that may be of
interest - Eligibility for Autofill
<https://github.com/w3ctag/design-reviews/issues/831>. This review is for a
proposal from Chrome to improve browser autofill in two key areas we have
seen affect payment forms:

1. Fill across distinct iframes on a page with the same origin. This
supports PSP products like Stripe Elements
<https://stripe.com/en-ca/payments/elements> or Adyen Components
<https://docs.adyen.com/payment-methods/cards/web-component> where each
input field on a site merchant.example/checkout is in a separate iframe (
psp.example/cc_number.html, psp.example/cc_expiry.html, etc). This is
already shipped in Chrome, but we are now trying to specify it formally.

2. Allow filling from the top-level site down into cross-origin iframes, as
long as a new 'Shared Autofill' permission policy is set. This would
support the common case we see where the "Cardholder Name" field (which is
usually the first field) is hosted on the top-level site (e.g.,
merchant.example) but the rest of the credit card fields are hosted in
cross-origin iframes (e.g., psp.example). This is not yet shipped in
Chrome, and is the core of the TAG review.

I expect to present this work in the August 3rd WPWG session to give folks
more context. *However* we don't want to block on waiting until then, so:

1. If you have feedback or questions on the feature, please feel free to
reply to this email thread or directly to myself.
2. If you wish to indicate support for the work, leave a short comment on the
TAG review <https://github.com/w3ctag/design-reviews/issues/831> indicating
your type of business (e.g., merchant, PSP, browser vendor, etc) and why
you support it.

Thanks,
Stephen

-- 
smcgruer • he / him