- From: schwering <notifications@github.com>
- Date: Thu, 29 Jun 2023 18:27:42 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/831/1613989213@github.com>
Hi Daniel, > We remain concerned with the level of information available to the user about what they have agreed to share with whom via auto-fill. Is it possible to advise UA providers to surface this information to the user in some way "are you OK with sharing your cc number with ecommerce site who uses payment provider as a payment provider?" We've considered this, but in the use-cases we see so far, we believe this wouldn't help the user in the frame-transcending (payment) forms we see today. There's a large number of payment service providers (900+ according to [Wikipedia](https://en.wikipedia.org/wiki/Payment_service_provider#Market_size)). And the PSP origins are often hard to recognise because they tend to be quite bulky (some examples: `assets.braintreegateway.com`, `secure-magenta1.be2bill.com`, `checkoutshopper-live.adyen.com`, `request.eprotect.vantivcnp.com`, `epgjs-rendercashier.easypaymentgateway.com`). > We also remain concerned about the multi-stakeholder buy in. If this is going to be adopted by the industry then we'd like to make sure it's widely adopted across browsers. We don't have explicit statements from [WebKit](https://github.com/WebKit/standards-positions/issues/141) or [Mozilla](https://github.com/mozilla/standards-positions/issues/752). However, payment service providers have voiced their interest. Happy to ask them to chime in here if you feel this is relevant. > Apart from that can you let us know any other status or updates? I think the [HTML PR](https://github.com/whatwg/html/pull/8801#pullrequestreview-1483578338) is close to getting approval. We've extended the example and note to elaborate when and why a browser many decide to fill across iframes. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/831#issuecomment-1613989213 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/831/1613989213@github.com>
Received on Friday, 30 June 2023 01:27:48 UTC