Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831)

Thank you all for the feedback and comments!

**Re @torgo**

We intend to pursue this in the WHATWG as part of the HTML spec, and are looking to drive consensus on the autofill definitions within that group.

**Re @cynthia**

1. The final positions on the proposal from [Mozilla](https://github.com/mozilla/standards-positions/issues/752) and [Apple](https://github.com/WebKit/standards-positions/issues/141) are pending and discussions are ongoing.
2. We agree. We suppose this would need cooperation of the implementors, [payment industry](https://en.wikipedia.org/wiki/Payment_Card_Industry_Data_Security_Standard), and payment service providers.
3. Acknowledged.

**Re @hober**

Thanks Tess (and Anne!); we do appreciate and agree that autofill is a user interface feature. However, we think there is value in giving web developers some structure around what they can roughly expect, and in particular we think specing shared-autofill as a clear (though non-binding) signal to the browser is valuable. Much like how autocomplete="cc-number" is a valuable signal for web developers to know about.

We're happy to work with Anne to find the right middle-ground of what to spec – see our [latest reply in the WebKit request for positions](https://github.com/WebKit/standards-positions/issues/141#issuecomment-1480536492) where we changed the text, and we can keep iterating on that!

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/831#issuecomment-1517032595
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/831/1517032595@github.com>